On Sep 7, 1:32 pm, Jim N <jim.nach...@gawker.com> wrote: > I was getting this when starting puppetmasterd (puppet- > server-0.25.5-1.el6.noarch RPM install): > > $ sudo /etc/init.d/puppetmaster start > Starting puppetmaster: Could not run: Could not create PID file: /var/ > lib/puppet/run/puppetmasterd.pid > > This change in the init script fixed the problem: > > #pidfile=/var/run/puppet/puppetmasterd.pid > pidfile=/var/lib/puppet/run/puppetmasterd.pid > > Is that a bug worth reporting?
I won't deny others' affirmative responses, but I do observe that Puppet has used /var/run/puppet as its pidfile location for a very long time (since at least 0.19). Over here, that directory is owned by puppet:puppet, which allows puppetmasterd to write its PID file there. The few other services that manage their own PID files appear to do it the same way -- mysqld, for example. John -- 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.
