| 1 |
I was watching this conversation to see how others do this sort of thing |
| 2 |
and am glad to have learned of dead.letter. Thanks. |
| 3 |
|
| 4 |
Incidentally, I typically do this sort of debugging by just redirecting |
| 5 |
output to a file. That is: |
| 6 |
|
| 7 |
* * * * * root <script> > /tmp/foo 2>&1 |
| 8 |
|
| 9 |
It always seems like the easiest way to go. |
| 10 |
|
| 11 |
-Jacob |
| 12 |
|
| 13 |
Aaron Walker wrote: |
| 14 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 15 |
> Hash: SHA1 |
| 16 |
> |
| 17 |
> Ben Munat wrote: |
| 18 |
> |
| 19 |
> | PS: or maybe there's somewhere that cron puts the output when it can't |
| 20 |
> | mail it? |
| 21 |
> |
| 22 |
> If you're running the script as root, mail it couldn't deliver would be |
| 23 |
> put in |
| 24 |
> /root/dead.letter. |
| 25 |
> |
| 26 |
> | |
| 27 |
> | Jonathan Rogers wrote: |
| 28 |
> | |
| 29 |
> |> |
| 30 |
> |> Yes, the programs in /etc/cron.* are running as root, but probably not |
| 31 |
> |> with exactly the same environment as when you run them from a login |
| 32 |
> |> shell. The cron daemon should mail the output from your script if it |
| 33 |
> |> fails. If you can get the error messages, I might be able to help. |
| 34 |
> |> |
| 35 |
> |> Jonathan Rogers |
| 36 |
> |> |
| 37 |
> |
| 38 |
> |
| 39 |
> - -- |
| 40 |
> Eat drink and be merry, for tomorrow we diet. |
| 41 |
> |
| 42 |
> Aaron Walker < ka0ttic@g.o > http://dev.gentoo.org/~ka0ttic/ |
| 43 |
> Gentoo/BSD | cron | shell-tools |
| 44 |
> http://butsugenjitemple.org/~ka0ttic/ |
| 45 |
> |
| 46 |
> -----BEGIN PGP SIGNATURE----- |
| 47 |
> Version: GnuPG v1.2.6 (GNU/Linux) |
| 48 |
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
| 49 |
> |
| 50 |
> iD8DBQFBlloKC3poscuANHARAja4AJ9qDNISjFWZlpDFd4jIzobQ8uh3rQCguO1t |
| 51 |
> y5+lQ06YyqeK58HvD2zRCpY= |
| 52 |
> =YsZz |
| 53 |
> -----END PGP SIGNATURE----- |
Archives