[mirror-admin] ideas for recognizing bitflips / dir changess

[ftp at secsup.org]

On Mon, 4 May 2009, Jan Kasprzak wrote:

> ftp at secsup.org wrote:
> : 6) publish in a machine parsable format the date/time (timestamp) that the
> : next release bit flip is going to happen. have some simple script on the
> : mirror site side that turns the simple-file into a cronjob which does the
> : requisite chmod 755 commands.
> :
> : I'm not sure much more machinery is really required, is it?
>
> 	I think the RSS as the transport channel for this info would be nice
> to have (and a sample script for downloading and parsing this, of course).

rss is pretty heavy weight if all you want is: "flip at HH:MM DD/MM/YYYY" 
isn't it?? It's a fine method for somethings, I just question the 
complexity for something that really doesn't require it.

something like: wget -O - fedora-release-url | grep "RELEASE" | at

seems like it'd be just dandy... (add some checking on the client side of 
course, but...)

>
> 	What I usually do, is to read the release date from the
> mirror-list message, and then set up an at(1) job (usually 3 minutes
> before the bit flip time) to do
>
> chmod -R a+rX $FEDORA_ROOT/linux/releases/$RELEASE
>
> (note the a+rX, 0755 is probably not always what you want).
>
> 	Of course should the release be cancelled for some reason,
> I may miss the information and publish it anyway. But then, releases
> are usually in a quite sane time in my time zone (4 pm CET).

yup, 10am EST is a little tough to remember sometimes :)

--