[8629] in Info-AFS_Redistribution
Re: automating 'vos release'
daemon@ATHENA.MIT.EDU (Jeff Blaine)
Mon Apr 16 11:38:18 2001
Date: Mon, 16 Apr 2001 11:32:55 -0400
From: Jeff Blaine <jblaine@linus.mitre.org>
To: David R Boldt <dboldt@usgs.gov>
cc: info-afs@transarc.com
Message-ID: <327779890.987420775@jblaine-pc.mitre.org>
In-Reply-To: <OF70E57C71.A2F61CE4-ON85256A30.0051CC41@er.usgs.gov>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
> This is going to require that we run a "vos release" on a periodic,
> automated basis.
Require?
I'm against the idea in concept, but that's an opinion. Why not do
it by hand (takes 3 seconds to type) when you know you want to
release for sure? Anyway...
> * if the read/write version of a volume has not changed since
> the last release, will "vos release" no-op, or will it try to
> synchronize anyway.
I believe what happens is that it will check out the replicas
(quickly), determine that they are up to date, and do nothing.
> * would it make sense to attempt to determine whether a volume
> has changed before doing a release? --I don't have a very good
> sense for how resource expensive "vos release" is.
Sure.
> if it would be a good idea to only release when necessary, is there
> a more efficient way to discover whether a read/write volume has
> changed since the last release other than comparing the mtimes
> of all directories in the volumes?
vos examine my.volume.name | grep 'Last Update'
> Is anyone else doing this sort of thing?
