Bryan J. Smith <b.j.smith at ieee.org> wrote: > From: Simon Perreault <nomis80 at lqt.ca> > > Sure, theoretically it would be possible, but how would you restart this one? > > [nomis80 at poste10-153 ~]$ sudo lsof | grep libc | grep init > > init 1 root mem REG 253,0 1521500 999437 /lib/tls/libc-2.3.5.so > > I need to verify the post-install script for the glibc RPM, but > I believe it SIGHUPs the process -- and SIGHUP tells GLibC to > reload itself for all new calls from any new process, while > leaving the old code available for running processes. If you can read binary :) The script section of the glibc RPM is a very simple one: [angenenr at shutdown dict]$rpm -q --scripts glibc postinstall program: /usr/sbin/glibc_post_upgrade.i686 postuninstall program: /sbin/ldconfig And I cannot find Documentation for glibc_post_upgrade at the moment, a "strings" on that binary doesn't really help either. Ralph -- Ralph Angenendt......ra at br-online.de | .."Text processing has made it possible Bayerischer Rundfunk...HA-Multimedia | ....to right-justify any idea, even one Rundfunkplatz 1........80300 München | .which cannot be justified on any other Tl:089.5900.16023..Fx:089.5900.16240 | ..........grounds." -- J. Finnegan, USC -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20050603/128864e9/attachment-0005.sig>