-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

At some point hitherto, Patrick R. McManus hath spake thusly:
> my guess is that it has to do with the output of one or both of these
> commands (the stdout/stderr output).. redirect them to /dev/null or a
> logifle and give it another try..

I'm inclined to agree... programs run by cron are generally expected
to have no output, or to have said output redirected somewhere.  This
is not a requirement, but otherwise output of the commands will get
mailed to root (unless other efforts were made to change that
behavior).

Since you haven't redirected anything, you may be able to determine
what went wrong by reviewing root's mail from cron.  There might also
be clues about the problem in the system logs...  A better approach to
debugging would be to redirect all output somewhere.


- -- 
Derek Martin               ddm@pizzashack.org    
- ---------------------------------------------
I prefer mail encrypted with PGP/GPG!
GnuPG Key ID: 0x81CFE75D
Retrieve my public key at http://pgp.mit.edu
Learn more about it at http://www.gnupg.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8/iP1djdlQoHP510RAtX4AJ9Y7Lvls83JaRGpnYtbsOrQDsdvdwCfeVmd
DNC+vsysXkyruE4Iajsv+H0=
=2TCW
-----END PGP SIGNATURE-----