[OpenAFS] 1.1.0 client on RH 7.1

[Rudolph T Maceyko]

We've upgraded afsd in-place for years...  You (rpm, actually) don't 
destroy the file with the old inode /usr/vice/etc/afsd points to... 
That gets moved aside and unlinked after a completely new 
/usr/vice/etc/afsd gets installed.  So afsd keeps running, the same as 
any other file would remain available when updated this way.

BTW, the reason we update afsd in-place is that we deliver nearly all 
of our software updates from /afs...  Right after the software is 
updated the box reboots to fully pick up any changes (normally that's 
the case anyway, when the update happens during the overnight automatic 
software update).

-Rudy

--On Monday, July 23, 2001 11:14:45 -0400 Derek Atkins 
<warlord@MIT.EDU> wrote:

> What happens when afsd disappears out from under your running system?
> I can see that being a Bad Idea (TM).  In the past, I even had the afs
> RPM shut down AFS in the process of upgrading, to be sure you didn't
> kill your system.  The reason is that I've seen systems crash hard
> when they lose afsd out from under them.
>
> -derek
>
> Rudolph T Maceyko <rtm@cert.org> writes:
>
>> The spec file for openafs-client lists /afs as a directory owned by
>> the  openafs-client RPM:
>>
>> %files client
>> %defattr(-,root,root)
>> %dir /afs
>>   .
>>   .
>>   .
>>
>> This precludes installing the RPM when AFS is running.  Our in-house
>> RPMs have not taken ownership of /afs, so we haven't run into this
>> prior to using the spec file from OpenAFS.
>>
>> 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  be %config?  I haven't tried that yet...
>>
>> -Rudy
>>
>> --On Monday, July 23, 2001 10:58:57 -0400 jgood@umbc.edu wrote:
>>
>> >    5:openafs-client         error: unpacking of archive failed on
>> >    file /afs: cpio: chown failed - Read-only file system