From: Rodrigo Barbosa rodrigob@suespammers.org
That, my friend, is very much true. Depending on the kind of server you are running (mumber of different processes), a reboot will be much easier. Did that myself a few times.
As far as examining running processes, one should have _good_ operational procedures and practices to track what is and isn't running on your system. If you can, stick with Sys-V start/kill init scripts for everything, and document anything that can't be (as well as why).
I don't like to rely on reboots to do such things. In fact, when building a new, standard system configuration, I like to shunt to "init 1" and back to "init 3" (run-levels assume distro is Fedora-based) several times to ensure that all my start/kill init scripts are proper.
That way I can stop and start user-space services piecemeal and completely.
-- Bryan J. Smith mailto:b.j.smith@ieee.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, Jun 02, 2005 at 12:42:47PM -0500, Bryan J. Smith b.j.smith@ieee.org wrote:
From: Rodrigo Barbosa rodrigob@suespammers.org
That, my friend, is very much true. Depending on the kind of server you are running (mumber of different processes), a reboot will be much easier. Did that myself a few times.
As far as examining running processes, one should have _good_ operational procedures and practices to track what is and isn't running on your system. If you can, stick with Sys-V start/kill init scripts for everything, and document anything that can't be (as well as why).
I don't like to rely on reboots to do such things. In fact, when building a new, standard system configuration, I like to shunt to "init 1" and back to "init 3" (run-levels assume distro is Fedora-based) several times to ensure that all my start/kill init scripts are proper.
That way I can stop and start user-space services piecemeal and completely.
Actually, there is another neat trick for rpm based systems.
You see, rpm, prior to removing anything, will rename that to ${NAME}.OLD. So, libc.so.6 becomes libc.so.6.OLD, and then removed.
As we all know, if that library is currently open by any running process, it won't be imediately removed (even tho you can't see it with a 'ls').
The trick is pretty simple: lsof | grep OLD
That, of course, only aplies if you are doing everything using RPM (yum, redhat-update, apt-get).
[]s
- -- Rodrigo Barbosa rodrigob@suespammers.org "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, Jun 02, 2005 at 12:42:47PM -0500, Bryan J. Smith b.j.smith@ieee.org wrote:
I like to shunt to "init 1" and back to "init 3" (run-levels assume distro is Fedora-based) several times to ensure that all
Allow me to make a small correction.
Even tho that will work on Linux, the correct way to communicate with the init process is using the 'telinit' command. Just calling init directly can cause you some severe headache on other platforms, and telinit will work on every unix-like system I've seen so far.
Also, run-levels are standarized, and should be the same on all unix-like platforms.
[]s
- -- Rodrigo Barbosa rodrigob@suespammers.org "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
-
Bryan J. Smith <b.j.smith＠ieee.org> -
Rodrigo Barbosa