Re: Bug#151305: Needs to restart cron (and probably others) on upgrade
>>>>> "Stephen" == Stephen Zander <email@example.com> writes:
>>>>> "Sam" == Sam Hartman <firstname.lastname@example.org> writes:
Sam> What do people think about this? I'm not sure doing a cron
Sam> restart on all pam upgrades is right.
Stephen> How else would you recover from this? I assume the
Stephen> underlying problem revolves around processes holding on
Stephen> to old libraries after new libraries are installed. As
Stephen> libc6 already has to deal with this issue it should be
I'd rather not deal in the pam package at all. I think the number of
cases of this type of issue are sufficiently small that pam should not restart anything on upgrade.
If there are explicit issues I'll restart the appropriate packages on
upgrade. Note that the version of pam under discussion s in
experimental; if it breaks things you get to keep all the pieces.
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org