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 before settling on a PID. Start-stop-daemon has no way to keep
track of such behaviour, and I know of no way to make Puppet write its own PID
to a file. So I patched the script.
The patch isn't completely fool proof, but we ran it in production for months,
and it's certainly better than no PID at all.
Is Ubuntu the place to offer such fixes? Or is it better to take them to
Debian, or to PuppetLabs?
** Affects: puppet (Ubuntu)
Importance: Undecided
Status: New
** 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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397898
Title:
incorrect PID in initscript
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1397898/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
