Bug#385012: init-script does not work if /usr is on a different filesystem

2006-09-12 Thread Craig Small
On Tue, Aug 29, 2006 at 04:13:48PM +0200, Bas Zoetekouw wrote: That's not correct. Although /usr/bin/which exists, it's a symlink to /bin/which, which _is_ available when /etc/init.d/procps is run As is mine: ls -l /usr/bin/which lrwxrwxrwx 1 root root 10 2006-07-24 16:42 /usr/bin/which -

Bug#385012: init-script does not work if /usr is on a different filesystem

2006-08-29 Thread Bas Zoetekouw
tag 385012 + moreinfo tag 385012 + unreproducible thanks Hi Sven! You wrote: /etc/init.d/procps is using which (located at /usr/bin/which) at a time where /usr is not mounted. That's not correct. Although /usr/bin/which exists, it's a symlink to /bin/which, which _is_ available when

Bug#385012: init-script does not work if /usr is on a different filesystem

2006-08-28 Thread Sven Hartge
Package: procps Version: 1:3.2.7-1 Severity: serious /etc/init.d/procps is using which (located at /usr/bin/which) at a time where /usr is not mounted. This causes the init-script to fail and leaves /etc/sysctl.conf unprocessed. The severity is justified by the fact that /etc/sysctl.conf is the