Perhaps I should turn logging back on and wait for the error to start again and then
post the output.
-Original Message-
From: Kevin Alexander Boyd [mailto:[EMAIL PROTECTED]
Sent: Monday, March 22, 2004 5:58 AM
To: Jason Ferguson
Cc: [EMAIL PROTECTED]
Subject: Re: Rsync killed my server
e:
> Date: Mon, 22 Mar 2004 05:49:56 -
> From: Jason Ferguson <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Rsync killed my server
>
>
> I have the following as a line in a script kicked off from cron:
>
> sudo rsync -e ssh -avz /Times_QPS/ 192.168.22.72
"Threw a mental" is extremely unhelpful. What was it writing to the
logfile?
Jason Ferguson wrote:
I have the following as a line in a script kicked off from cron:
sudo rsync -e ssh -avz /Times_QPS/ 192.168.22.72:/Times_QPS/ --eahfs
It logs the output to a log file, however rsync caused the
I have the following as a line in a script kicked off from cron:
sudo rsync -e ssh -avz /Times_QPS/ 192.168.22.72:/Times_QPS/ --eahfs
It logs the output to a log file, however rsync caused the log file to go to an 80gb
file and fill up my disk because it threw a mental when a file it went to sy
