Mailinglist Archive: opensuse-project (96 mails)

[Per Jessen <per@xxxxxxxxxxxx>]

Rob OpenSuSE wrote:

> 2009/11/19 Per Jessen <per@xxxxxxxxxxxx>:
>
> > To me, what is worthwhile testing is something I determine.  It is in
> > no way influenced by what may or may not have been tested already.
> > I will often try out the alphas/betas/RCs on boxes I might be
> > prepping for production, or a box that has been taken out of
> > production, but not yet moved. Right now I've got a new firewall box
> > sitting next to me, running 11.2.
>
> Yes that's good opportunism.

Yeah, that's really what it is - testing on current (i.e. production
hardware) is out of the question, whereas anything "in transition" is
easier to get to.

> > I looked at the smolt package, and AFAICT, Henne Vogelsang added a
> > requirement for cron back in 2008, so maybe that's when the cron-file
> > was created too. Maybe Henne had some specific idea wrt the 0120 time
> > to run smolt?
>
> I used to avoid the sleep issues in a simple way by having the cron
> job, create a job with randomised later time into an  at(1) queue
> configured 1 job wide and like the batch(1) queue to run only when
> system load was low.  That way the job would get run, even if there
> was downtime and   you didn't need processes hanging around.

Run smolt on startup, skipping if timestamp of <last-time-file> is less
than 30 days old. 

> If we can't use the info gathered effectively, there seems little
> point in taking a look at the upstream code, and writing & trying to
> get them to accept a SuSE specific patch which works better with our
> dumber cron(8) system.

I don't see this as being an upstream issue, I think it's about
packaging.  


/Per Jessen, Zürich

--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx