One more comment: avoid runnig other large processes (like backups) while
your cron.daily is running (often defaults to 2..4 am). Log rotation and
analysis of large log files may interfer with a process that works on the
same files.
My preference for crontabs is to keep and edit them as regular file(s)
and start them with
crontab [-u root] crontabFileName
(the -u option was suggested on older systems when you su into root as
another user... it just became a habbit) ........... Horst
On Mon, 16 Dec 2002, Rob Hudson wrote:
> Ah, so I don't need the user to run as in a user specific cron? Make
> sense. Thanks.
>
> > On 20021216.2203, Bob Miller said ...
> >
> > Rob Hudson wrote:
> >
> > > I'm trying to get a shell script to run every Saturday morning at 4am.
> > > Instead of editing /etc/crontab like I usually do, i thought I'd set it
> > > up in my user crontab.
> > >
> > > I ran crontab -e as my user, and added the following:
> > >
> > > 0 4 * * 6 rob /home/rob/bin/bkup
> > >
> > > Which runs my backup script. Is there something else I need to do? The
> > > timestamps on the files say it didn't run this weekend.
> >
> > Remove the word, "rob", unless you have a command called rob in the
> > system's default path.
> >
> > You should have been mailed an error when rob was not found -- is mail
> > set up on this machine?
> >
> > --
> > Bob Miller K<bob>
> > kbobsoft software consulting
> > http://kbobsoft.com [EMAIL PROTECTED]
> > _______________________________________________
> > Eug-LUG mailing list
> > [EMAIL PROTECTED]
> > http://mailman.efn.org/cgi-bin/listinfo/eug-lug
> _______________________________________________
> Eug-LUG mailing list
> [EMAIL PROTECTED]
> http://mailman.efn.org/cgi-bin/listinfo/eug-lug
>
_______________________________________________
Eug-LUG mailing list
[EMAIL PROTECTED]
http://mailman.efn.org/cgi-bin/listinfo/eug-lug
