Your message dated Mon, 08 Feb 2010 09:45:51 +0100
with message-id <[email protected]>
and subject line Incorrect PIDFILE [...]
has caused the Debian Bug report #562056,
regarding puppet: Incorrect PIDFILE="/var/run/${NAME}.pid" in init script
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
562056: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562056
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: puppet
Version: 0.25.1-3
Severity: normal
Should be PIDFILE="/var/run/puppet/${NAME}.pid"
Otherwise puppet fails to remove pid file on stop or restart.
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (700, 'stable'), (600, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages puppet depends on:
ii adduser 3.110 add and remove users and groups
ii facter 1.5.1-0.1 a library for retrieving facts fro
ii libopenssl-ruby 4.2 OpenSSL interface for Ruby
ii libruby [libxmlrpc-ruby 4.2 Libraries necessary to run Ruby 1.
ii libshadow-ruby1.8 1.4.1-8 Interface of shadow password for R
ii libxmlrpc-ruby 4.2 transitional dummy package
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
ii ruby1.8 1.8.7.72-3lenny1 Interpreter of object-oriented scr
Versions of packages puppet recommends:
ii libaugeas-ruby1.8 0.2.0-2 Augeas bindings for the Ruby langu
ii rdoc 4.2 Generate documentation from ruby s
puppet suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
fixed 562056 0.25.4-1
thanks
Hello,
I believe the recent upload of 0.25.4-1 fixes this issue.
--
Stig Sandbeck Mathisen
--- End Message ---
