On 11 October 2010 23:45, Vic l...@beer.org.uk wrote:
After adding the folder that holds the file to
$PATH and then changing crontab to run from /folder/file.sh it would not
run But when I changed it to /folder/file it ran?
Yes - exactly,
The name of your script was day1, IIRC. That's its
On Tuesday 05 October 2010 21:52:53 Vic wrote:
OK - here are a couple of problems...
crontab -l
0 0 * * 1 /backup.day1.sh # Day 1 backup
(the same was repeated for each of the other 4 scripts)
Note that this is trying to run /backup.day1.sh . You probably don't mean
that; the dot
On Mon, 11 Oct 2010 18:25:36 +0100, xendis...@gmx.com said:
Thanks for all the help I have now have it working, not sure exactly
what the problem was
Two comments, not meant to sound harsh (but I'm aware that they may do).
Firstly, there's no need to quote an entire thread just to say that
On Monday 11 October 2010 18:41:25 Keith Edmunds wrote:
Two comments, not meant to sound harsh (but I'm aware that they may do).
Firstly, there's no need to quote an entire thread just to say that you
have things working now.
Secondly, you can approach Linux from a number of perspectives,
(like the file I wanted crontab to run only needed the file name not the
.sh on the end of it)
That *is* the filename.
foo.sh is the name of a file. foo is the name of another file. These are
not the same file.
If you tell the OS to execute a file called foo.sh, then foo.sh is the
name of
On Monday 11 October 2010 22:28:06 Vic wrote:
(like the file I wanted crontab to run only needed the file name not the
.sh on the end of it)
That *is* the filename.
foo.sh is the name of a file. foo is the name of another file. These are
not the same file.
If you tell the OS to execute
After adding the folder that holds the file to
$PATH and then changing crontab to run from /folder/file.sh it would not
run But when I changed it to /folder/file it ran?
Yes - exactly,
The name of your script was day1, IIRC. That's its name - calling it
day1.sh doesn't work, because that's
Sorry if I have asked this question before, but I am still beating my head
against the wall with it.
I have Ubuntu server 10.04 with xfce desktop. I have a small script (in fact
there are 5 but more of that in a minute) that runs an rsync command for backup
purposes, if I run this script from
So my first question is, where should these 5 scripts reside (they
currently live in a folder called backup in the root of the file sytem)
Wherever you like. Just make sure you tell cron the full pathname to the
script = ./day1 is unlikely to work, because that means the day1 script
in the
On 05/10/10 18:25, Vic wrote:
So my first question is, where should these 5 scripts reside (they
currently live in a folder called backup in the root of the file sytem)
Wherever you like. Just make sure you tell cron the full pathname to the
script = ./day1 is unlikely to work, because that
On 05/10/10 18:49, John Cooper wrote:
On 05/10/10 18:25, Vic wrote:
[snip excellent advice]
How do I get cron to run them and where do I find any logs files that
may
point to what is going wrong?
show us the output of
crontab -l
as the user who owns these scripts?
plus
ls -l
On Tuesday 05 October 2010 19:15:06 Stuart Sears wrote:
On 05/10/10 18:49, John Cooper wrote:
On 05/10/10 18:25, Vic wrote:
[snip excellent advice]
How do I get cron to run them and where do I find any logs files that
may
point to what is going wrong?
show us the output of
crontab
The output of 'the ps ax | grep crond' is just showing you the grep command
running, and not the actual cron daemon. I'm sure I've seen some systems
where cron is not running as a daemon, but I may be wrong, and this may have
been a very long time ago... But if you're getting emails about cron,
Please also bear in mind that running the script from the /backup directory
itself - with ./day1.sh - may yeild different results than running it from
another working directory with /backup/day1.sh
You may want to adjust your script to cd to whatever working directory you
want the script to use,
14 matches
Mail list logo
