Re: Upgrading libc6 problem
Vinod Kurup wrote:
>
> On Tue, May 29, 2001 at 05:22:00PM +0200, Michel D?nzer wrote:
> > Vinod Kurup wrote:
> >
> > > I just did an apt-get upgrade on my unstable powerpc machine and it
> > > upgraded libc6.
> > >
> > > shortly thereafter, I started getting this message in my syslog:
> > >
> > > May 28 22:10:05 localhost inetd[2673]: getpwnam: mail: No such user
> > >
> > > And my mail stopped being delivered. Thanks to the magic of google, I
> > > found this message from Colin Watson:
> > >
> > > <http://lists.debian.org/debian-devel-0009/msg01990.html>
> > >
> > > Quoting:
> > >
> > > > Going down to single-user mode and then back up to runlevel 2 seems to
> > > > have fixed most such problems. Sending a SIGHUP to inetd, as libc6's
> > > > postinst does via '/etc/init.d/inetd restart', is not enough - it
> > > > needs to be stopped and started again.
> > >
> > > So i went to runlevel 1 and then back to 2 and everything was back to
> > > normal. Just thought I'd mention it in case it happens to anyone
> > > else.
> >
> > /etc/init.d/inetd restart
> >
> > wouldn't do?
>
> Actually, you're right - it should do. I should have tried that first, but
> I just went for the big hammer.
>
> The problem (I think) is that the libc6 postinst script calls
> /etc/init.d/inetd restart before some other important piece is upgraded. At
> least, that's what I gather from reading the rest of the thread I
> referenced above.
In fact, the post the link points to is a bit contradictory. It says
/etc/init.d/inetd restart just sends SIGHUP to inetd (which of course can be
not enough), but at least on this box it stops and starts it. Maybe
libc6.postinst really uses /etc/init.d/inetd reload or force-reload? That
would be a bug in either libc6 or inetd then.
--
Earthling Michel Dänzer (MrCooper) \ Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast \ XFree86 and DRI project member
Reply to: