Bug#385012: init-script does not work if /usr is on a different filesystem
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 - /bin/which It appears in debianutils, mine is 2.16.2 We really need some more information about why this fails. Thanks Bas for the heads-up about this too. - Craig -- Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 Eye-Net Consulting http://www.enc.com.au/ MIEE Debian developer csmall at : enc.com.au ieee.org debian.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385012: init-script does not work if /usr is on a different filesystem
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 lrwxrwxrwx 1 root root 10 2006-07-24 16:42 /usr/bin/which - /bin/which It appears in debianutils, mine is 2.16.2 We really need some more information about why this fails. It was really my fault, a combination of a procps backport to Sarge (where which is in /usr/bin) and a to quick and wrong investigation fonr by me. So to make this clear: There is _NO_ bug in the Sid procps package, just in the backported one, which needs a different init-script which does not rely on which, because in Sarge which is not available at the time the init script is run. I already closed the bug as soon as I realized my error. Sorry for the noise and trouble. S° -- Sven Hartge -- professioneller Unix-Geek Meine Gedanken im Netz: http://www.svenhartge.de/
Processed: Re: Bug#385012: init-script does not work if /usr is on a different filesystem
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 filesystem Tags were: moreinfo Tags added: unreproducible thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385012: init-script does not work if /usr is on a different filesystem
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/init.d/procps is run This causes the init-script to fail and leaves /etc/sysctl.conf unprocessed. Also, I can't reproduce this here. I have /usr on a seperate filesystem on all my machines, and procps runs fine on all of them. Could you please give some more info on which problem you encountered, exactly? Maybe your PATH wasn't set correctly or so? -- Kind regards, ++ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385012: init-script does not work if /usr is on a different filesystem
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] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385012: init-script does not work if /usr is on a different filesystem
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 libc62.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 psmisc22.3-1 Utilities that use the proc filesy -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]