help-cfengine
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Turning off update.conf


From: Chip Seraphine
Subject: Re: Turning off update.conf
Date: Mon, 28 Apr 2003 14:04:57 -0500
User-agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.2.1) Gecko/20030121

Yes; it is very handy for dealing with a broken cfagent.conf or the like. The problem is that if update.conf itself is broken, it fails right away.

Someone replied to me off-list and pointed out that explicitly naming the cfagent file via "-f" command will bypass the update.conf file; this works fine, and is presumably the reason The Author did not find a "--no-update" type of flag was not needed.

Steve Bergeon wrote:

Why would you want to ignore update.conf? It purpose is to allow you to recover
from the distribution of faulty config files.

"Imagine what would happen if you made a mistake in the configuration, i.e. a
syntax error which got distributed to every host. Now all the hosts would be
unable to run cfengine, and thereafter unable to download a corrected
configuration file. The whole setup would be broken. To prevent this kind of
accident, a separate configuration file is used to copy the files and binaries
to each host. This configuration should be simple, and should almost never be
edited: they key word here is reliability."

http://www.cfengine.org/docs/cfengine-Tutorial.html#Building%20a%20distributed%2
0configuration






reply via email to

[Prev in Thread] Current Thread [Next in Thread]