On 12/02/2014 12:21 AM, Matthaus Owens wrote:
Sorry, I should have said pidfile is written to $rundir/agent.pid.
$rundir defaults to $vardir/run if not specified in puppet.conf.
Thank you! Now my config works, and this 'bug' report should never have
existed. :)
--
You received this bug
Version data:
Ubuntu Trusty
Puppet 3.4.3-1 0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1397898
Title:
incorrect PID in initscript
To manage notifications about this bug go to:
The attachment Patch to make Puppet initscript find the PID of the
daemon seems to be a patch. If it isn't, please remove the patch
flag from the attachment, remove the patch tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Is Ubuntu the place to offer such fixes?
It should go to Debian in the first instance, assuming that Debian is
also affected - in Ubuntu, we try to keep the packaging in sync with
Debian.
** Changed in: puppet
It should go to Debian in the first instance, assuming that Debian is
Ok. Then it'll have to wait until I can confirm that Debian is affected
as well.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
The puppet agent writes its own pidfile, to $vardir/run/agent.pid
depending on what is in puppet.conf. If you are seeing problems with
that, I would encourage you to open a bug upstream.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Sorry, I should have said pidfile is written to $rundir/agent.pid.
$rundir defaults to $vardir/run if not specified in puppet.conf.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
