On Friday 09 May 2008, Valery Reznic wrote: > Why you don't put this cron jobs to run say every 1 hour, so it'll not to > took your months for debugging ?
That might be a good idea, but I haven't done it for 2 reasons: 1 - I don't want to crash my system at a random time. At least, now that I know the problem always occurs at 2:02 in the morning, I can make sure I have an up-to-date backup before the crash 2 - I'm not sure if running some of these daily jobs on an hourly basis might cause unforseen problems. I'm including the list again, in case anyone can comment on the dangers, if any. [EMAIL PROTECTED] cron.daily]$ ls -l total 56 -rwxr-xr-x 1 root root 276 2007-08-17 02:56 0anacron* -rwxr-xr-x 1 root root 2575 2007-09-01 13:56 awffull* -rwxr-xr-x 1 root root 396 2007-11-16 23:00 getskyepg* -rwxr-xr-x 1 root root 400 2007-08-28 21:44 hylafax* -rwxr-xr-x 1 root root 37 2007-01-28 19:59 logcheck* -rwxr-xr-x 1 root root 180 2007-07-19 23:57 logrotate* -rwxr-xr-x 1 root root 410 2007-08-31 01:48 makewhatis.cron* -rwxr-xr-x 1 root root 137 2007-09-24 17:26 mlocate.cron* lrwxrwxrwx 1 root root 27 2008-01-02 05:56 msec -> /usr/share/msec/security.sh* -rwxr-xr-x 1 root root 431 2006-02-05 22:56 my-aa-findlargefiles* lrwxrwxrwx 1 root root 26 2008-01-02 20:16 myRPMlist -> /data1/myscripts/myRPMlist* -rwxr-xr-x 1 root root 167 2005-01-10 12:51 reoback* -rwxr-xr-x 1 root root 118 2007-10-02 12:09 rpm* -rwxr-xr-x 1 root root 101 2007-11-20 19:55 tetex.cron* -rwxr-xr-x 1 root root 371 2007-08-08 18:35 tmpwatch* -rwxr-xr-x 1 root root 315 2007-09-05 13:24 tripwire-check* -- Shlomo Solomon http://the-solomons.net Sent by KMail (KDE 3.5.7) on LINUX Mandriva 2008.0 ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
