Cronatb problems? Putin in the new plane to the overall increase in household crontab-e regular operations. But no schedule? /usr/spool/cron/crontabs Are defined by the user name in the paper. /usr/lib/cron Directory structure : -rw-r----- 1 Jul 28 1596 05:11 root cron. Proto -rw-r----- 1 Jul 28 1596 05:11 root cron. Proto.b -rw-rw---- Root cron 0 1 Jul 28 05:12 at.deny -rw-rw---- Root cron 0 1 Jul 28 05:12 cron.deny P---rw---- 1 0 Oct 8 10:46 FIFO cron cron -rw-rw---- Bin cron 0 1 Jul 28 05:11 log -r-xr--r-- One root sys 1701 Jul 28 05:11 logchecker -rw-r--r-- 1 cron sys 17 Jul 28 05:11 queuedefs Ordinary ah? ? How else? ? ? Another asked if the implementation of regular operations like Monday to Friday, Field is the fifth such -5? achieved : 0 (Is it possible? ) Cronatb problems? To restart the server? If it is directly kill cron, how kill. I have a direct kill and then implement /etc/cron& Incorrect report : ! Can not start cron; FIFO exists Fri Oct 8 15:09:28 2004 ! ******* ******** CRON ABORTED Fri Oct 8 15:09:28 2004 Cronatb problems? Search about Forum, wrote a cron sdccf the complete manual. Cronatb problems? # Rm /usr/lib/cron/FIFO # /etc/cron Cronatb problems? How /etc/cron need parameters? Cronatb problems? Direct execution on the trip The operation is going to join you #crontab l If not implemented, the proposed log opened cron : Both were CRONLOG /etc/default/cron changed. Up the cron, and then check /usr/lib/cron/log Cronatb problems? -rw-rw---- 1 adm cron 2491 Jul 28 05:11 adm Oct 8 1596 09:52 -rw-rw---- 1 jft cron jft -rw-rw---- One root cron 815 Jul 28 05:12 mmdf -rw-rw---- 1 Sep 9 1102 10:21 root root cron -rw-rw---- 1 Jul 28 05:11 sys sys cron 752 1 Jul 28 05:11 bin cron 811 -rw-rw---- uucp Jft users include : /usr/jft/bin/I8040ht 8040& 32 7 * * * 00 23 * * * /usr/jft/bin/I8061sndxy Cronatb problems? Thank you CNL : Crontab-l is carrying out operations to join. How to restart cron? Cronatb problems? Oh, we did not see in front of CNL, now see, # Rm /usr/lib/cron/FIFO # /etc/cron Cron has reopening of the only try try Cronatb problems? Swap first kill FIFO document again swap rm Restart cron Cronatb problems? Halo : M /usr/lib/cron/log ! Cron started *** *** Fri Oct 8 15:57:39 2004 pid = 25585 "; CMD : /usr/jft/bin/I8040sndjf (to implement) "; Fri Oct 8 15:59:00 2004 25851 c jft "Jft Fri Oct 8 15:59:00 2004 25851 c Rc=137 137 return to the old crew are good. It appears normal, ah? How to implement unsuccessful? Cronatb problems? /usr/jft/bin/I8040sndjf Implementation document normal! ! ? ? /usr/jft/bin/I8040sndjf Manual on implementation. Cronatb problems? Maintain proper checks whether the environmental variables, cron implementation of all the things needed to set up their own environmental variables, such as PATH Cronatb problems? Agree that the CNL Cronatb problems? Now the problem has been identified environmental variables. But not find a solution. 24 17 * * * /bin/su - jft-c "/usr/jft/bin/I8040sndjf 1>;/tmp/1.log 2>;/tmp/2.log" nor do Cronatb problems? [ Closed window ]