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

[Matt Domsch]

On Mon, May 04, 2009 at 11:16:06AM +0200, 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).
> 
> 	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).
> 
> -Yenya

just FYI, 'at' appears not to honor Daylight Savings Time.

$ cat mail-matt | at 14:00 UTC
$ atq
5 2009-05-04 08:00 a mdomsch

That should be 09:00 not 08:00.  That's not a reason not to use it,
but could be annoying, and shouldn't affect systems that run in UTC
always.  It means we need to be sure to schedule it such that running
an hour earlier is still fine.

-- 
Matt Domsch
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux

--