-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-09-11 at 17:03 +0200, stephan beal wrote:
Now that you mention that...
Another problem happens depending on the editor used for cron files: if the timestamp of the dir holding the modified file doesn't change (act. the modtime), cron does not notice. This is documented, in fact. I remember that joe or mcedit had that problem, but I don't remember which one.
i was using 'pico' - don't know if that's affected.
No, I just tested it. cer@nimrodel:~/tmp/p> l total 12 drwxr-xr-x 2 cer users 6 2006-08-29 20:06 ./ drwxr-xr-x 14 cer users 4096 2006-07-02 00:13 ../ cer@nimrodel:~/tmp/p> pico file cer@nimrodel:~/tmp/p> l total 16 drwxr-xr-x 2 cer users 17 2006-09-11 19:38 ./ drwxr-xr-x 14 cer users 4096 2006-07-02 00:13 ../ -rw-r--r-- 1 cer users 4 2006-09-11 19:38 file You see that the date of the directory changed. I tried again with mcedit and joe: both are ok in 10.1. Last time I tried this was in 9.3 and one failed, probably mcedit. Interesting... maybe someone read us when we where talking about it here las time :-)
The jobs are indeed now running. i can't explain why they didn't initially run. After creating a couple "bogus" jobs which only echo and such, and setting the cron time to "far" in the future (15 minutes), it appears to work. Stupid, but true.
Well... good that they work, even if we are not sure why... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFBaA1tTMYHG2NR9URAgkIAJ4xe1YrnfVrGcVat7rNgxPPvcaR4gCfSmwI rjlJsZKzQDBv4IwCREkQoNM= =IhdK -----END PGP SIGNATURE-----