On Tue, Nov 30, 2010 at 12:30 AM, wrote:
> The cron job was too long and truncated. I guess last time it truncated
> at "/media/2tb/"
>
Ouch! That's a painful cron bug. One easy way to shorten your command is
to switch to using --exclude-from=FILE and put all your includes/excludes in
that fi
"created directory /media/2tb/bak/da"
The cron job was too long and truncated. I guess last time it truncated at
"/media/2tb/"
Any guesses on where the command length limit is? Cron? bash? It sure
would be nice for cron to spit out an error if I create a job that's too
long.
--
"I don't wan
Hello,
Recording the output (standard error and standard out) to a log file will help
with investigating this issue if it is reproducible. Perhaps another person on
this list will provide a better suggestion.
In addition, perhaps adding some additional debugging information before and
after th
I expect this is user error, but I thought I'd post in case anyone else is
feeling a similar sense of losing their mind.
I have a root cron job:
0 3 * * * rsync -Hva --stats --del ... / /media/2tb/bak/dancer-`date +\%F`/
"..." represents 4 --link-dest's and 22 --exclude's (including /media/)
