nate a écrit :
> Niki Kovacs wrote:
>
>> Now I don't have the slightest clue why this doesn't work. What's the
>> magic word here ?
>
> You check the cron log? maybe it ran it just had an error so
> it didn't produce the results you expected.
>
In fact it ran OK. Only the result wasn't as expec
Dianne wrote:
> On Oct 30, 2009, at 9:29 AM, Niki Kovacs wrote:
>> Now here's what I have on the local backup server :
>>
>> [r...@grossebertha:~] # crontab -l
>> 24 17 * * * /usr/local/bin/sauvegarde.sh
>
> You may have checked already, but make sure that crond is running,
> i.e. /sbin/service cro
Niki Kovacs wrote:
> Now I don't have the slightest clue why this doesn't work. What's the
> magic word here ?
You check the cron log? maybe it ran it just had an error so
it didn't produce the results you expected.
It's also good to send STDOUT/STDERR to a file for easier debugging
of cron stuf
On Oct 30, 2009, at 9:29 AM, Niki Kovacs wrote:
Now here's what I have on the local backup server :
[r...@grossebertha:~] # crontab -l
24 17 * * * /usr/local/bin/sauvegarde.sh
You may have checked already, but make sure that crond is running,
i.e. /sbin/service crond status. I get crond (pid
Hi,
I have a strange problem here. I have two servers, one dedicated
webserver, and a local backup server.
On the webserver I have this :
[r...@12569hpv163154:~] # crontab -l
00 22 * * * /usr/local/bin/sauvegarde-pmbccps.sh
This launches a backup script every day at 22:00, and it works as expe
5 matches
Mail list logo