From: Donncha O Caoimh (donncha.ocaoimh at domain tradesignals.com)
Date: Tue 20 Apr 1999 - 17:10:41 IST
Well, www.tradesignals.com is still running so I guess that upgrade
worked.. *wipes brow*
Donncha.
Kenn Humborg wrote:
>
> Vincent Cunniffe wrote:
> >
> > >> I figured out what it was - the glibc I'm using has a memory leak and
> > >> the bug is reported in the mysql docs. Has anyone upgraded the glibc
> > >> of a running system? (through RPM..) Any side effects or possible
> > >> crashes I should know about?
> > >
> > >I've upgraded the glibc of a running Debian system through dpkg/dselect
> > >many times, without trouble. I don't imagine Red Hat Linux could be
> > >substantially worse.
> >
> > How does that work... it keeps a copy of the original glibc in memory for
> > all of the processes which loaded it dynamically, loads in a new copy for
> > anything started after the upgrade, and finally loses the old copy when the
> > last process using it terminates?
>
> That's exactly it. In fact, I once upgraded from RH4.x to 4.x+1 without
> rebooting. Simply upgraded all the RPMs I had installed for which never
> versions came on the newer CD.
>
> Watch out if you have a small root partition as the older lib.so files
> won't be deleted until all processes are finished with it. You won't
> see the older files listed in directories but they are still there
> taking up space.
>
> Hopping down to single-user mode and back up again will clear them out
> with affecting the uptime shown by the uptime command :-)
>
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:04:08 GMT