[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#151305: Needs to restart cron (and probably others) on upgrade



On Sun, Jun 30, 2002 at 09:37:55PM -0700, Stephen Zander wrote:
> >>>>> "Sam" == Sam Hartman <hartmans@debian.org> writes:
>     Sam> What do people think about this?  I'm not sure doing a cron
>     Sam> restart on all pam upgrades is right.

> How else would you recover from this?  I assume the underlying problem
> revolves around processes holding on to old libraries after new
> libraries are installed.  As libc6 already has to deal with this issue
> it should be relatively easy to lift code to do this for PAM libaries
> as well.

AIUI, the problem with glibc is that some services will fail to run
correctly after upgrading if they are NOT restarted, whereas the problem
with libpam is that some services will fail to run correctly after
upgrading if they ARE restarted.  In the first case, a restart is
desirable because we don't want to break users' machines on upgrade; but
in the second case, restarting services is only a debugging aid for
spotting library bugs more easily.  I don't see these cases as
particularly analogous, and don't think that packages should be designed
around the assumption that bugs will not be fixed.

Steve Langasek
postmodern programmer

Attachment: pgpw3SFd7e_Jm.pgp
Description: PGP signature


Reply to: