<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:Courier New,courier,monaco,monospace,sans-serif;font-size:10pt">So '> /path/to/my.log' is not sufficient for capturing error messages? Then I need a review of the basics because why do I see error messages when I run a command from the command line?<br><div><br></div><div style="font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:10pt"><br><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> jacob <jborer@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> CLUE's mailing list <clue@cluedenver.org><br><b><span style="font-weight: bold;">Sent:</span></b> Thu, June 2, 2011 9:35:56 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [clue] [TECH] rsync command runs
from command line but not via cron<br></font><br>
<br><br><div class="gmail_quote">On Thu, Jun 2, 2011 at 9:16 AM, Brian Gibson <span dir="ltr"><<a rel="nofollow" ymailto="mailto:bwg1974@yahoo.com" target="_blank" href="mailto:bwg1974@yahoo.com">bwg1974@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
It looks like specifying the full path to ssh did it. Duh. I'm just surprised<br>
it silently failed since output was being redirected to a file.<br>
<div><div></div><div class="h5"><br></div></div></blockquote><div><br></div><div> If you want errors to go to the log file you need to redirect stderr to stdout. (Shell errors generally go to stderr, file descriptor 2, not stdout, file descriptor 1.) Add 2>&1 to end of the cron definition.</div>
<div><br></div><div>-jacob</div></div><br>
</div></div>
</div></body></html>