[OpenAFS] 1.1.0 client on RH 7.1

Rudolph T Maceyko rtm@cert.org
Tue, 24 Jul 2001 11:10:29 -0400

The "usual" practice may be that, but we've never done it for AFS.  It's usually NOT been possible to stop and restart AFS, anyway...

Anyway, to get back to the original issue...  I'm going to try marking /afs in the spec file as %config(missingok) to see if that works.  I'll add mkdir -p /afs or
somesuch in %post so it's there.  I still don't know whether rpm will allow a directory to be treated this way...


--On Monday, July 23, 2001 19:48:27 +0200 Paolo Saggese <NOSPAM@lngs.infn.it> wrote:

> 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...