On Wed, 25 Feb 2004, Mathias Haas wrote:
> Oh my! What stupidity! Of course. I'm afraid sometimes my DOS-roots are
> revealed... Thanks!
In general, you ought to be aware that cron sets up only a minimal
environment. If you want your scripts to run predictably then you
probably ought to ensure t
> On Tue, 24 Feb 2004 17:56:49 +0100 (CET)
> [EMAIL PROTECTED] wrote:
>
>> Hello guys! I have two questions about shellscripts:
>
> Your second question seems to have been addressed, so here's something
> for your first question...
>
>> 1) I have a backup job that 'tar's a lot of files and currentl
On Tue, 24 Feb 2004 17:56:49 +0100 (CET)
[EMAIL PROTECTED] wrote:
> Hello guys! I have two questions about shellscripts:
Your second question seems to have been addressed, so here's something
for your first question...
> 1) I have a backup job that 'tar's a lot of files and currently I
> redirec
Julien Gabel wrote:
The following works fine, here is the detail:
$ date ; ls -lF /tmp/test.*
Tue Feb 24 22:50:11 CET 2004
-rwxr-x--- 1 jgabel wheel 49 Feb 24 22:50 /tmp/test.bash*
$
$ cat /tmp/test.bash
#!/usr/local/bin/bash
echo start > /tmp/test.txt
$
$ crontab -l
* * * * * /tmp/test.bash
$
>> The following works fine, here is the detail:
>>
>> $ date ; ls -lF /tmp/test.*
>> Tue Feb 24 22:50:11 CET 2004
>> -rwxr-x--- 1 jgabel wheel 49 Feb 24 22:50 /tmp/test.bash*
>> $
>> $ cat /tmp/test.bash
>> #!/usr/local/bin/bash
>> echo start > /tmp/test.txt
>> $
>> $ crontab -l
>> * * * * * /t
Julien Gabel wrote:
As a reply to both answers, here's a script that wont' run:
#!/usr/local/bin/bash
echo start > test.txt
...and here is bash:
[EMAIL PROTECTED] /usr/local/etc]>> whereis bash
bash: /usr/local/bin/bash
this is /var/log/cron
Feb 24 19:20:00 p3-550 /usr/sbin/cron[27988]: (root) CMD
>> As a reply to both answers, here's a script that wont' run:
>> #!/usr/local/bin/bash
>> echo start > test.txt
>>
>> ...and here is bash:
>> [EMAIL PROTECTED] /usr/local/etc]>> whereis bash
>> bash: /usr/local/bin/bash
>>
>> this is /var/log/cron
>> Feb 24 19:20:00 p3-550 /usr/sbin/cron[27988]: (
Mathias Haas wrote:
Julien Gabel wrote:
Hello guys! I have two questions about shellscripts:
2) The same backup job - is written as a bash script, and it works
perfectly when run by hand, but it won't run as a cron job.
Are you using a full path in the shebang at the top of the script?
Such a
You might wanna check the users mailbox. Cron send mail on errors.
Drew
On Tue, 2004-02-24 at 16:11, Mathias Haas wrote:
> It is executable and it didn't have a newline at the end, it does now -
> but there's still no difference...
> Do you have to do something to get FreeBSDs (4.6.2) cron to
It is executable and it didn't have a newline at the end, it does now -
but there's still no difference...
Do you have to do something to get FreeBSDs (4.6.2) cron to run
shellscripts?
..and I can still run the script "by hand"
Lowell Gilbert wrote:
Mathias Haas <[EMAIL PROTECTED]> writes:
Mathias Haas <[EMAIL PROTECTED]> writes:
> As a reply to both answers, here's a script that wont' run:
> #!/usr/local/bin/bash
> echo start > test.txt
Is it executable?
Does the last line have a newline at the end?
___
[EMAIL PROTECTED] mailing list
htt
Hello guys! I have two questions about shellscripts:
2) The same backup job - is written as a bash script, and it
works perfectly when run by hand, but it won't run as a cron job.
>>> Are you using a full path in the shebang at the top of the script?
>>> Such as:
>>>
>>> #!/bin/sh
>
Julien Gabel wrote:
Hello guys! I have two questions about shellscripts:
2) The same backup job - is written as a bash script, and it works
perfectly when run by hand, but it won't run as a cron job.
Are you using a full path in the shebang at the top of the script?
Such as:
#!/bin/sh
or
#!
>> Hello guys! I have two questions about shellscripts:
>> 2) The same backup job - is written as a bash script, and it works
>> perfectly when run by hand, but it won't run as a cron job.
> Are you using a full path in the shebang at the top of the script?
> Such as:
>
> #!/bin/sh
> or
> #!/usr/l
[EMAIL PROTECTED] wrote:
Hello guys! I have two questions about shellscripts:
2) The same backup job - is written as a bash script, and it works
perfectly when run by hand, but it won't run as a cron job.
Are you using a full path in the shebang at the top of the script? Such as:
#!/bin/sh
or
Hello guys! I have two questions about shellscripts:
1) I have a backup job that 'tar's a lot of files and currently I redirect
all output of the job to a log. Tar unfortunately lists all directories
that it goes through, even if nothing is 'tar'ed in those directories. So
my logfile contains all
16 matches
Mail list logo
