On 8/25/06, Matthew Miller <mattdm@xxxxxxxxxx> wrote: > On Fri, Aug 25, 2006 at 08:59:09AM -0400, seth vidal wrote: > > This feels like it is a function of the openafs package being updated > > but I don't know what's going on here from this. > > So, here's another weird thing. On systems where AFS was busy when it > tried to stop it -- part of the openafs-client preuninstall check which only > runs when $1=0 (that is, on package erase), everything ended up running > fine. But what in the world would cause it to even *try* if it's updating, > not removing? > The preuninstall script is called when any package is removed, including the older version. I think the "$1 = 0" guard means the script is passed the number of that package left. Anything that needs to done only when the last package is removed needs the guard. Unguard preuninstall scripts are rare. But postuninstall ones are fairly common, mainly to ru ldconfig and update caches. And there are even a few that only run if one or more is left to restart daemons after config changes. - Ian
