Wil Cooley wrote: > What seems like it would be fairly straightforward to implement > would be a user-initiated locking mechanism, so that a locked file > would not be updated but an alert generated that the file was wrong > date/checksum/etc. Something like this: > > # cflock /etc/httpd/conf.d/foo.conf > # vi /etc/httpd/conf.d/foo.conf > # cflock -u /etc/httpd/conf.d/foo.conf
I just do "killall cfagent; killall cfexecd" (or pkill) and start them back up when I am done with my tests. I have a cron job that reports if the correct cfengine processes are not running on a box in case I forget to turn them back on or in case they go away for some other reason. The only reason I could see needing more sophisticated locking is if some other human is likely to restart cfengine without communicating with the admin doing the ad-hoc changes. Best, Brendan -- Senior System Administrator The University of Chicago Department of Computer Science http://www.cs.uchicago.edu/people/brendan _______________________________________________ Help-cfengine mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-cfengine
