Your message dated Tue, 29 Aug 2006 17:05:41 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#385012: init-script does not work if /usr is on a 
different filesystem
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
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
preferred way to set networking parameters (like forwarding etc.) in Etch,
which breaks if one is using this version of procps.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-cks1-198
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages procps depends on:
ii  libc6                        2.3.6.ds1-4 GNU C Library: Shared libraries
ii  libncurses5                  5.5-2       Shared libraries for terminal hand

Versions of packages procps recommends:
ii  psmisc                        22.3-1     Utilities that use the proc filesy

-- debconf-show failed


--- End Message ---
--- Begin Message ---
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 backported
package to Sarge (where which is only in /usr/bin).

I am very sorry for the noise I made, I will take my business with this
problem back to the backports.org mailinglist.

Grüße,
Sven.

-- 
Sven Hartge -- professioneller Unix-Geek
Meine Gedanken im Netz: http://www.svenhartge.de/

Achtung, neue Mail-Adresse: [EMAIL PROTECTED]

--- End Message ---

Reply via email to