Executive summary: how best can cfengine-3 be used to control various
"chkconfig XXX {on|off}" things in Redhat/CentOS?
Detail:
Until a couple of years ago, in my previous job, I used cfengine-2
extensively to manage many UNIX machines of several varieties and
versions of operating systems.
In my new place, we're just starting with cfengine, so naturally are
looking at version 3 rather than version 2. (Quite a change, especially
after not having been near either version for a long time!)
Whilst I'm making reasonable progress, I'm stuck on a particular aspect.
(And I also have a gut feeling that this aspect ought to be one of
those areas where the v2 to v3 changes may perhaps have greatly improved
matters.)
On a typical Redhat/CentOS type of system, not only is there the concept
of stop/start/reload of processes ("service XXX {stop|start|...}") but
there is also the concept of the service being enabled for boot-time
("chkconfig XXX {on|off}", etc.). And other OSes have similar concepts.
I'm reasonably comfortable using cfengine-3 process promises to handle
the "service XXX{stop|start|...}" procedures. But what is the cleanest
cfengine-3 way to manage "chkconfig XXX {on|off}"?
The information isn't leaping out of the documentation. But a pointer
to a suitable manual page might be OK for me.
(Using "cfengine-community-3.1.4", by the way.)
--
: David Lee
: ECMWF (Data Handling System)
: Shinfield Park
: Reading RG2 9AX
: Berkshire
:
: tel: +44-118-9499 362
: email: [email protected]
_______________________________________________
Help-cfengine mailing list
[email protected]
https://cfengine.org/mailman/listinfo/help-cfengine
