package puppetmaster
clone 378382 -1
close 378382 0.20.1-1
severity -1 normal
retitle -1 puppetmaster daemon should fail to start if PID file cannot
be properly written
notfound -1 0.18.2-1
found -1 0.20.1-1
thanks
On 07/01/07, Paul TBBle Hampson <[EMAIL PROTECTED]> wrote:
Alex, try adding
File.open(@pidfile + ".%d" % $$, "w") { |f| f.puts $$ }
...
Thanks for your help.
It seemed my problem was user error... /var was full. The root user
could still set pid files as I have 5% reserved for root on /var but
the puppet user could not write the contents of the puppetmaster pid
file it would seem.
In summary my testing shows that if there is space available in
/var/run then the current (0.20.1-1) init script works. Paul Hampson's
statement:
I just tried the same procedure Alex R. Owen tried, on
an unstable powerpc box, and the PID file was created
fine, and had a PID in it, and puppetmaster stopped when
the init.d script told it to.
Seems to confirm that the init scripts in version 0.20.1-1 work. I am
therfore closing this bug as fixed in 0.20.1-1. However I am also
going to clone this bug at the severity normal as
pupetmasterd should fail to start if it cannot write it's PID file
(for example in the case when /var if full !!!)
I hope you all agree.
Regards
Alex Owen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
