Observed results (Was: Re: [cobalt-users] crontab & exec problem.)

[Jeff Lasman <jblists@xxxxxxxxxxxxx>]

Jeff Lasman wrote:

> Steve Werby wrote:
> 
> > A good a reason as any.  I thought maybe it was a solution to avoid running
> > it at a time when too many programs were running that gave false positives.
> > I suppose chkrootkit just isn't an early bird on your boxes.  <g>
> 
> In fact yes, that's why I didn't want it running before 6 am.  Now I'm
> thinking however that the next program won't run until after this
> program waits, so I'll just delay everything two hours.  Oh, well, I'm
> willing to give that a one-day trial.  I don't care what time it runs as
> long as nothing else is running at the same time.  I'll probably move it
> tomorrow to someting like zzz-chkrootkit or similar.

I've left it running as chkrootkit with the two-hour delay so it'll run
at 6 am.  While I haven't checked carefully, I believe, based on looking
at what's actually happening on my system, that the way cron works is
that it starts every script in the cron.daily directory, one after the
other, without delays, so it may be necessary to put delays into
cron-jobs you don't want running too quickly.

Anyway, my new cron job runs close to 6am every morning, and that works
for me <smile>.  The other cron jobs seem to work at the same time they
used to work... I'll be doing more checks, and if anyone can verify
exactly who cron works from experience, and save me the effort, that
would be appreciated <smile>.

Jeff
-- 
Jeff Lasman <jblists@xxxxxxxxxxxxx>
Linux and Cobalt/Sun/RaQ Consulting
nobaloney.net, P. O. Box 52672, Riverside, CA  92517
voice: +1 909 778-9980  *  fax: +1 909 548-9484