|
Home > Archive > Debian Developers > June 2006 > Why is procps procps.sh in init.d?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Why is procps procps.sh in init.d?
|
|
| Craig Small 2006-06-25, 7:53 pm |
| Hello,
I've been looking at bug #343620 where /etc/init.d/procps.sh should
not exit out. I can see why this could cause problems.
However, while I can see that bug #52228 asks for procps to be sourced,
I can see no good reason for doing so.
Isn't the whole point of the /etc/init.d/<whatever>.sh files to setup
environment variables for subsequent init scripts.
The procps init script sets kernel variables, when you remove all the
stuff what it basically does is
/sbin/sysctl -p
Which sets the kernel variables found at /etc/sysctl.conf
Is there any good reason keeping it like that, it appears to be it
would be best to make it /etc/init.d/procps
- 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 debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Petter Reinholdtsen 2006-06-26, 7:36 am |
|
[Craig Small]
> Isn't the whole point of the /etc/init.d/<whatever>.sh files to setup
> environment variables for subsequent init scripts.
Nope. The point of .sh init.d scripts is to speed up the boot. The
sourcing is not guaranteed when scripts are executed in parallel, so
all scripts should work when executed in a separate process as well.
Friendly,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
|
|