[OpenAFS] Last Update not updating?

[Kim Kimball]

I'd also like to see this option for "vos exa"

I know of several locations that use the vos exa update time to 
determinie if a vos release is required.

This is especially important for cells with far flung fileservers over 
low bandwidth links who are providing "vos release" capabilities to end 
users via a srvtab/keytab or other mechanism.  One former client 
discovered that the end users were likely to call "vos release" without 
being sure if the volume had been updated or not.  "Just in case."

We used the vos exa update times to filter out volumes whose RW parents 
had not been updated relative to the ROs.

Kim Kimball



Horst Birthelmer wrote:
> 
> On Jan 11, 2006, at 5:40 AM, Mike Polek wrote:
>> The vos release won't actually do any volume copying
>> if things are already up-to-date, but it takes a lot
>> longer to issue a vos release on a set of, say, 10
>> volumes than to check the dates and release the
>> one that has been updated.
>>
>> Any chance of adding a switch to the vos exam command
>> so that if you do something like
>>
>> vos exam my.vol -sync -cell pictage -local
>>
>> you get the old behavior, and without the -sync
>> you get the new behavior? If I issue the 10
>> vos release commands, it will have to sync
>> anyway, and apparently do a lot more stuff.
>> Since I'm interested in the Last Update
>> field, it would be helpful to have a way to
>> make sure it's accurate. For the times when
>> I don't care, of course the new behavior is
>> preferable.
>>
>> Just a thought.
> 
> Not a bad idea, since the client application decides which call it uses.
> 
> As Jeff mentioned, it's inaccurate for about 25 min.
> So, this matters just for 25 minutes, than your tools would probably 
> work as before.
> 
> Horst
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info