Issue #1856 has been updated by ianburrell.

An alternative is to change the pidfile to be /var/run/puppet.pid.  The 
killproc function in /etc/init.d/functions used by stop will get the pid from 
/var/run/puppetd.pid before pidof is available.  

The PIDFILE in /etc/init.d/puppet is /var/run/puppet/puppet.pid.  And the 
default rundir in puppet.conf is /var/run/puppet.  Unfortunately, I don't see a 
way to tell killproc to use a different pidfile.  I don't think this should be 
changed by default but you could change /etc/sysconfig/puppet and puppet.conf 
to use a different pidfile.
 
----------------------------------------
Bug #1856: redhat init script doesn't honor pidfile on shutdown/reload
http://projects.reductivelabs.com/issues/1856

Author: mfournier
Status: Needs design decision
Priority: Normal
Assigned to: lutter
Category: Red Hat
Target version: 
Complexity: Trivial
Affected version: 0.24.7
Keywords: redhat init script shutdown cron


When puppet is run "by hand" and something happens to run "service puppet stop" 
at the same time, puppet get's killed because the initscript calls "pidof 
puppet" instead of checking if a pidfile exists.

This is an problem when puppet is configured to be run by cron and is 
instructed to ensure no puppet service is running. Puppet sort of kills himself 
halfway through the job.

Attached is a patch which solves the issue.


----------------------------------------
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to