Hmm, that _assumes_ that we all use the same CellServDB.global file.
Incorrect assumption.

A better solution is to provide a means for us to use our own CellServDB file
(and not stomp on it with the next RPM install).
--
cheers
paul http://acm.org/~mpb

Derek Atkins wrote:

I'm away on vacation, but I've been sent code for the SPEC file to
_generate_ CellServDB at runtime from a CellServDB.global (replaced
with the RPM) and a CellServDB.local (where you place your local
information). This change will go into future (read: 1.2.9) RPMs.

-derek

Deniz Akkus Kanca <[EMAIL PROTECTED]> writes:


Hello,

Currently the RH RPM, openafs-client overwrites /usr/vice/etc/CellServDB and saves the original as /usr/vice/etc/CellServDB.rpmsave

I looked at the spec file for building the RPMs:
The line: %config /usr/vice/etc/CellServDB

can be changed to: %config(noreplace) /usr/vice/etc/CellServDB

in which case, RPM does not overwrite the /usr/vice/etc/CellServDB already present, but puts in the new file as /usr/vice/etc/CellServDB.rpmnew

I'd like to suggest that this behavior is preferable. I find the current behavior problematic since I use a modified CellServDB that includes just our cell and updating via RPM on a number of clients has been cumbersome due to the present behavior of writing over CellServDB.
Best regards,
Deniz



_______________________________________________
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info



_______________________________________________
OpenAFS-info mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-info


Reply via email to