SUMARY: cron job question

From: bbb bb (mccux1@hotmail.com)
Date: Mon Jun 19 2006 - 13:37:23 EDT


Thanks to so many answer.

SUN cron daemon will NOT re-read /avar/spool/cron files withour use "crontab
-e".

Redhat linux will re-read /var/spool/corn every minutes. That is reason why
LINUX work on both way.

DOC from LINUX man parge:

Additionally, cron checks each minute to see if its spool directory's
modtime (or the modtime on
       /etc/crontab) has changed, and if it has, cron will then examine
the modtime on all crontabs and reload those which have changed. Thus cron
need not be restarted whenever a crontab file is modified. Note that the
  Crontab(1) command updates the modtime of the spool directory whenever it
changes a crontab.

>On 6/19/06, bbb bb <mccux1@hotmail.com> wrote:
> We have Solaris 8 on SUN Ultra server. I found if I use "vi" edit
>/var/spool/cron/crontab/root. It will NOT work. For example put "##"
>before statement , it still run that cron job.
>
>If I use "crontab -e" . it will work.
>
>ON Redhat LINUX, both way will work.
>
>Can anyone tell mw why ?
>
>Thanks.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:40:10 EDT