On 12/01/2014 10:42 PM, Stig Sandbeck Mathisen wrote:
> That's a delightfully evil hack. Will using an upstart job work instead,
> or do you need to keep track of the PID there, as well (something for
> post-start, then)?
Matthaus Owens of Puppet Labs responded that Puppet *does* write its own
PID
Jurjen Bokma writes:
> ** Patch added: "Patch to make Puppet initscript find the PID of the daemon"
>
> https://bugs.launchpad.net/bugs/1397898/+attachment/4271933/+files/puppet-init.patch
That's a delightfully evil hack. Will using an upstart job work instead,
or do you need to keep track o
Public bug reported:
Abstract:
Puppet initscript doesn't record the correct PID. WIth this patch, it does.
Longer version:
When the Puppet agent daemon gets started, /etc/init.d/puppet records a PID in
/var/run/puppet/${NAME}.pid, but it is the wrong one. Puppet may fork half a
dozen times befo
