Hi there,

I have two SH jobs I've always run manually in the past and would like
to have them run once a week automatically using cron.. I looked on
the internet for examples of running SH jobs and used crontab -e to
create this:

[root@alice jeff]# cat /var/spool/cron/root
45 12 * * 0 root /bin/sh /home/jeff/jeffbkup.sh
11 3 * * 6 root /home/jeff/rsynchbkup.sh

When each scheduled job fires off, I get an email from Cron_Daemon
with this message:

/bin/sh: root: command not found

This endeavor seemed pretty straight forward and after adding /bin to
my path and still getting the above message, I'm kinda stumped now.
Any suggestions or any more info I can offer? Thanks!

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Tue, 12 Aug 2008 19:04:00 -0400, jeff goudie wrote:

> Hi there,
>
> I have two SH jobs I've always run manually in the past and would like
> to have them run once a week automatically using cron.. I looked on
> the internet for examples of running SH jobs and used crontab -e to
> create this:
>
> [root@alice jeff]# cat /var/spool/cron/root
> 45 12 * * 0 root /bin/sh /home/jeff/jeffbkup.sh
> 11 3 * * 6 root /home/jeff/rsynchbkup.sh
>
> When each scheduled job fires off, I get an email from Cron_Daemon
> with this message:
>
> /bin/sh: root: command not found
>
> This endeavor seemed pretty straight forward and after adding /bin to
> my path and still getting the above message, I'm kinda stumped now.
> Any suggestions or any more info I can offer? Thanks!

Reread the crontab manual page. User's crontabs have only six (!)
fields, not seven. Only the global /etc/crontab has seven fields.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Michael Schwendt wrote:

On Tue, 12 Aug 2008 19:04:00 -0400, jeff goudie wrote:


Hi there,

I have two SH jobs I've always run manually in the past and would like
to have them run once a week automatically using cron.. I looked on
the internet for examples of running SH jobs and used crontab -e to
create this:

[root@alice jeff]# cat /var/spool/cron/root
45 12 * * 0 root /bin/sh /home/jeff/jeffbkup.sh
11 3 * * 6 root /home/jeff/rsynchbkup.sh

When each scheduled job fires off, I get an email from Cron_Daemon
with this message:

/bin/sh: root: command not found

This endeavor seemed pretty straight forward and after adding /bin to
my path and still getting the above message, I'm kinda stumped now.
Any suggestions or any more info I can offer? Thanks!


Reread the crontab manual page. User's crontabs have only six (!)
fields, not seven. Only the global /etc/crontab has seven fields.


Also, if you want them run only one a week, you might just put a script
to run them in /etc/cron.weekly unless you need better control over when
they run.....


--
Kevin J. Cummings
kjchome@rcn.com
cummings@kjchome.homeip.net
cummings@kjc386.framingham.ma.us
Registered Linux User #1232 (http://counter.li.org)

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Tue, Aug 12, 2008 at 1:04 PM, jeff goudie <jrgoudie@gmail.com> wrote:
>
> [root@alice jeff]# cat /var/spool/cron/root
> 45 12 * * 0 root /bin/sh /home/jeff/jeffbkup.sh
> 11 3 * * 6 root /home/jeff/rsynchbkup.sh
>
> When each scheduled job fires off, I get an email from Cron_Daemon
> with this message:
>
> /bin/sh: root: command not found

Remove the word 'root' from both lines?

I'm not positive, but if the two scripts have the proper #!/bin/sh
line in them, putting /bin/sh in the crontab line should also be
unnecessary.

Dave

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list