[OpenAFS] 1.1.0 client on RH 7.1

Jeffrey Hutzelman jhutz@cmu.edu
Tue, 24 Jul 2001 17:45:34 -0400 (EDT)

On Mon, 23 Jul 2001, Paolo Saggese wrote:

> On Monday 23 July 2001 17:06, Rudolph T Maceyko wrote:
> >[...]
> > It seems like a good idea to have /afs listed in the RPM database, but
> > then again it seems (to us anyway) to be a good idea to be able to
> > update AFS on a running system.
> >
> > I'm not sure what you can do about it...  Can you mark a %dir to also
> Well, when you upgrade a package which provides some service, the usual 
> practice is to add some preinst/postinst script to the RPM in order to 
> stop the service before the upgrade (preinst run /etc/init.d/afs stop) 
> and start it again after the upgrade has completed (i.e. start again in
> the postinst script).
> I guess this is what you'd like to have in the OpenAFS spec file, too...

Not really.  For one thing, AFS doesn't always deal well with being
shut down and restarted.  You can really lose if you try to shut down AFS
while there are open files (unmounting /afs will fail, and the rest of the
shutdown process will hang, possibly forever).  Even if that weren't the
case, other things can break.

In any event, /afs is not a config file; it's a mount point.  It should be
created by the postinstall script, and doesn't belong in the RPM database
at all.

-- Jeffrey T. Hutzelman (N3NHS) <jhutz+@cmu.edu>
   Sr. Research Systems Programmer
   School of Computer Science - Research Computing Facility
   Carnegie Mellon University - Pittsburgh, PA