On 02/27/2011 04:56 PM, shawn wilson wrote:
On Sun, Feb 27, 2011 at 1:32 PM, Boyd Stephen Smith Jr.<
b...@iguanasuicide.net> wrote:
In<4d685bbb.2010...@gmail.com>, Aaron Toponce wrote:
More garbage. There are _many_ good reasons to reboot a UNIX or
GNU/Linux server:
* Forcing applications to use the new libraries.
Poor reason; I've never found an application that needed a reboot to fix
this. (Yes, you need to restart the application, but not the OS.)
lets look at this for a second. lets look at the libraries that init uses:
swilson@swilson-mbp-vdebian:~/catalyst/New/lib/New/Controller$ ldd
/sbin/init
linux-vdso.so.1 => (0x00007fffe94c1000)
[snip]
hummm, so libc6 was updated on january 11, when did i last reboot this box?
swilson@swilson-mbp-vdebian:~/catalyst/New/lib/New/Controller$ uptime
19:28:15 up 41 days, 17:35, 6 users, load average: 1.72, 0.72, 0.26
so, i'm pretty sure that whatever got fixed in libc6 is not fixed on this
box if it deals with the base library. maybe i'm wrong - i'm pretty sure
it's possible to link a new library to a running process but i don't know.
and i don't know whether the dpkg scripts will do this whenever a new
library is installed for a running process.
/sbin/init is the only process that can't be forced to use a newly
installed library w/o rebooting. Every other process can.
/usr/sbin/checkrestart in package debian-goodies tells you what
processes are using obsolete libraries and can usually tell you
which services to restart.
--
I prefer banana-flavored energy bars made from tofu.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d6ae34c.50...@cox.net
