> > (1) How about looking for my snapshot announcements in p5p
> > (or "patchlevel.h" updates in perl5-changes) and launching smokes
> > from them, not from some arbitrary points in time?
> >
> > (2) Add a (cronjob?) suspend-all option to the smoke harness:
> > basically, send a SIGSTOP signal for all the participating machines
> > and process) that can be sent at 07:30am? (Coupled with a
> > continue-all, SIGCONT, when the next 22:45 arrives). The stopped
> > processes will consume virtual memory, not much else.
> >
> > (3) Some extensions of (2) would be kill-all, SIGKILL
> > dealt over the whole smoke cluster, and shutdown-all (SIGHUP
> > with graceful cleanup handler).
>
> Or - much more simple - rsync from the snap, instead of from current. We've
> discussed that option long while back, when you decided at that point in time
> that you'd prefer the current rsync over the snap rsync.
Can't remember my reasoning any more...
> To what should I change
>
> rsync -avz rsync://ftp.linux.activestate.com/perl-current/ .
>
> to get the latest snap
>
> rsync -avz rsync://ftp.linux.activestate.com/perl-snap/ .
rsync://ftp.funet.fi/perlsnap/
That has the problem that I do not update the snap daily, so there
should be a check in the smoke harness for "already done that".
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
