Hey Keith and Puppet-Users, the --pidfile option is passed to start-stop-daemon when starting. and the file /var/run/puppetd.pid is created, it just does not contain the pid. it contains
$ cat /var/run/puppetd.pid $ pet$ that is not the string "pet", it is a repeat of the prompt, so some non printable character is contained in /var/run/puppetd.pid It looks like exec() on puppetd is not returning a pid in the expected format from start-stop-daemon. the man page for puppetd does not list a --pidfile option. Cheers, Trevor On Mar 31, 1:28 pm, Keith Edmunds <k...@midnighthax.com> wrote: > On Tue, 31 Mar 2009 11:54:01 -0700 (PDT), mailtrevh...@gmail.com said: > > > "/etc/init.d/puppet stop" does not work because the /var/run/ > > puppetd.pid file does not contain the pid. > > What do you have in /etc/puppet/puppetd.conf under [puppetd]? Anything > relating to where the PID file is written? > > The pidfile here is /var/run/puppet/puppetd.pid: > > $ ps -p $(cat /var/run/puppet/puppetd.pid) > PID TTY TIME CMD > 13459 ? 00:17:05 ruby > > Keith --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
