Package: chef Version: 0.8.16-4.2 Severity: important /etc/init.d/chef-client thinks the PID for the daemon is in /var/run/chef- client.pid
/etc/chef/client.rb writes the PID for the daemon to /var/run/chef/client.pid Spot the difference? As a result, "/etc/init.d/chef-client start" will always fail (even though the daemon is started); "/etc/init.d/chef-client restart" will throw an error and not restart the daemon as it cannot kill the existing instance; and logrotate will be unable to tell the daemon to restart when the log is rotated, breaking logging. This renders chef-client useless as a daemon, and functional only on the command line. -- System Information: Debian Release: squeeze/sid APT prefers maverick-updates APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500, 'maverick-backports'), (500, 'maverick') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-24-generic (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
