Re: [cobalt-users] crontab & exec problem.

[Jeff Lasman <jblists@xxxxxxxxxxxxx>]

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.

> If you want it to run at a specific time, consider using a user cron (user
> root) so you can set the exact time.  I know we were involved in a thread,
> probably on this list, where we discussed system cron verse user cron.

This was an easy way to do it <smile>.  Yes, a user cron for root would
allow it to run at a specific time, BUT that was the approach the
original poster was having trouble with, and I've always just dropped
things into system cron, so that's what I tried.  When it worked, I
reported it to the list <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