In my reading I just ran across this:
[Puppet - Bug #7273] Modifying puppet.conf causes 'reparsing
config'
and TERM signal results in shutdown of daemon
short version: puppet agent can commit suicide, but it can't raise
itself from the dead.
However, init is immortal, and so puppetd can be, too.
# on debian squeeze as root:
insserv -r puppet
echo "7:2:respawn:/usr/sbin/puppetd --no-daemonize" >> /etc/inittab
init Q
If you don't want puppet running
init 3
or some other run level. puppetd will stop.
When you
init 2
puppetd will start again.
When you
killall puppetd
puppetd will do this:
Jun 30 01:28:20 vm01 puppet-agent[7548]: Caught TERM; calling stop
Jun 30 01:28:21 vm01 puppet-agent[8157]: Starting Puppet client
version 2.6.2
Jun 30 01:28:22 vm01 puppet-agent[8157]: Finished catalog run
in 0.11 seconds
I'm not seeing a downside to this. Am I missing something?
--
vagn
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
