Um 21:32 Uhr am 12.09.06 schrieb 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
> lrwxrw
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 -> /bi
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
Yes, correct. This bug is totally bogus (and totally my fault for not
researching correctly), because this only exists if using a backpor
Processing commands for [EMAIL PROTECTED]:
> tag 385012 + moreinfo
Bug#385012: init-script does not work if /usr is on a different filesystem
There were no tags set.
Tags added: moreinfo
> tag 385012 + unreproducible
Bug#385012: init-script does not work if /usr is on a different filesyste
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 /etc
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 th
6 matches
Mail list logo
