Adam Megacz wrote: > Derrick J Brashear <[EMAIL PROTECTED]> writes: >> 3) a small set of options, like afsdb, which i think should default to on > > I'll look into figuring out how this is done. It would also be nice > if it defaulted to on for Windows (unless it already does?) and Linux > (I'm pretty sure it doesn't).
The Windows AFS client service defaults to off. The Windows AFS installer defaults to on. This is how it should be configured for other platforms as well. >> Changing to afsdb by default mid-1.4 does offer some possible >> confusion, but given some other changes which (basically need to) >> appear in 1.4.5 perhaps it won't be that confusing compared to other >> things. > > Unless my understanding is incorrect, I don't think that adding -afsdb > can ever cause any functionality which was previously working to stop > working. Doesn't viced only check for AFSDB records if the cell is > not found in CellServDB? Turning on AFSDB records will result in two unwanted behaviors. (1) Administrators who install a restricted CellServDB file to limit the accessible cells will no longer find their client's restricted to the specified list (2) Users will experience delays where there weren't any before when accessing /afs/foobar where foobar is not a cell listed in either CellServDB or DNS. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
