Issue #5246 has been updated by Hunter Haugen.
Currently confirmed on Puppet 2.6.4 shipped with PE 1.2 as well as the last merge of 2.7.x, commit 25213bfcd0c3bf1b5b59131d91490268b4949374. - If `puppet agent --onetime` is run, it drops a pid file and doesn't clean it up. - If `puppet agent --onetime --no-daemonize` is run then it never places a pid file. - If `puppet agent` is forked into the background and killed via `kill` then it cleans up its pid file. ---------------------------------------- Bug #5246: Puppetd does not remove it's pidfile when it exits https://projects.puppetlabs.com/issues/5246 Author: R.I. Pienaar Status: Accepted Priority: High Assignee: Category: Target version: 2.7.x Affected Puppet version: 2.6.2 Keywords: mcollective Branch: When running puppetd it should delete its pid file when it exits <pre> root 20572 2.0 0.5 116736 35256 ? Ss 23:10 0:00 /usr/bin/ruby /usr/sbin/puppetd --onetime --splaylimit 30 --splay </pre> The pid file /var/run/puppet/agent.pid would have 20572 as expected, the puppet run completes ok: <pre> Nov 9 23:11:27 xen1 puppet-agent[20572]: Finished catalog run in 19.68 seconds </pre> But it leaves the pid file on the disk after exiting -- 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://projects.puppetlabs.com/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.
