On Mon 05 Nov 2001 15:50, Jarkko Hietaniemi <[EMAIL PROTECTED]> wrote:
> > > (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/
BTW If I'd forward Nick's latest smoke from colon, I'd be forwarding 24k with
the same error messages.
Since more and more smokers are entering the arena from all over the world,
just maybe we should (ask Jarkko to) update the perlsnap on a daily basis :-PP
--
H.Merijn Brand Amsterdam Perl Mongers (http://www.amsterdam.pm.org/)
using perl-5.6.1, 5.7.2 & 629 on HP-UX 10.20 & 11.00, AIX 4.2, AIX 4.3,
WinNT 4, Win2K pro & WinCE 2.11. Smoking perl CORE: [EMAIL PROTECTED]
http:[EMAIL PROTECTED]/ [EMAIL PROTECTED]
send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
