From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: glibc 2.1 -> 2.2 gotchas?
Date: Sat, 25 Aug 2001 15:54:17 -0700 [thread overview]
Message-ID: <20010825155417.A8892@nevyn.them.org> (raw)
In-Reply-To: <20010825154233.S14302@cpe-24-221-152-185.az.sprintbbd.net>; from trini@kernel.crashing.org on Sat, Aug 25, 2001 at 03:42:33PM -0700
On Sat, Aug 25, 2001 at 03:42:33PM -0700, Tom Rini wrote:
>
> On Sun, Aug 26, 2001 at 12:31:37AM +0200, Michel D?nzer wrote:
>
> > > What I recommend won't hurt and can certainly help flush older shared
> > > libraries out of memory.
> >
> > The point is probably that in the Debian packages, the maintainer scripts take
> > care of the necessary steps, so the user doesn't have to.
>
> This always got me tho... If a program is already running, how do you
> make it stop using the old libraries? If 'restarting' /sbin/init makes it
> reload, I'll take your word at it. But what about all of the other apps that
> happen to be running? The bash session I happen to be doing this upgrade
> from. Or X (yes, in an ideal world, you goto single user to do this
> anyhow.. :))
They keep running with the old libc. No big deal, really :) The RAM
will basically not be reclaimed until after you reboot.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-25 22:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-25 14:55 glibc 2.1 -> 2.2 gotchas? Keith Clayton
2001-08-25 15:31 ` Kevin B. Hendricks
2001-08-25 15:35 ` Michel Dänzer
2001-08-25 15:42 ` Kevin B. Hendricks
2001-08-25 15:55 ` Kaoru Fukui
2001-08-25 17:44 ` Kevin B. Hendricks
2001-08-25 18:06 ` Kaoru Fukui
2001-08-25 22:31 ` Michel Dänzer
2001-08-25 22:42 ` Tom Rini
2001-08-25 22:54 ` Daniel Jacobowitz [this message]
2001-08-26 4:36 ` Tom Rini
2001-08-29 21:08 ` Daniel Jacobowitz
2001-08-26 14:52 ` Keith Clayton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010825155417.A8892@nevyn.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).