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 :-)
Later,
Kenn
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
