Path: utzoo!mnetor!uunet!steinmetz!ge-dab!codas!ablnc!maxwell
From: maxwell@ablnc.ATT.COM (Robert Maxwell)
Newsgroups: comp.unix.questions
Subject: Re: Cron
Message-ID: <435@ablnc.ATT.COM>
Date: 22 Jan 88 16:19:03 GMT
References: <11098@brl-adm.ARPA> <449@wa3wbu.UUCP> <6621@agate.BERKELEY.EDU>
Organization: AT&T, Maitland, Florida
Lines: 23
Summary: crontab(1) UNIX SV User Reference Manual

In article <6621@agate.BERKELEY.EDU>, mwm@eris (Mike (My watch has windows) Meyer) writes:
> In article <1988Jan17.235014.19530@lsuc.uucp> dave@lsuc.UUCP (David Sherman) writes:
> <Every cron that I have ever seen or heard of either rereads crontab
> <every minute or so
> 
> Crontab? SysV doesn't have a "crontab". It has a /usr/lib/cron, which
> is full of little crontab files[*].

In System V, crontab(1) is a command that makes, lists or removes a users
crontab file. The use of the command to copy a file (or standard input)
to /usr/lib/cron/crontabs directory signals cron to reexamine the crontab
files to update it's schedule of cron jobs. (Read the man page for a
detailed description)
The system administrator can restrict access to the crontab(1) and at(1)
commands. The default on all distributions I have worked with only allow
root, sys, adm or similar administrative logins access to the commands
and the administrator has to change it to allow others to use it.

-- 
-----------------------------------------------------------------------------
Bob Maxwell	AT&T DP&CT	     |	All standard (and most non_standard)
Maitland, FL	ihnp4!ablnc!maxwell  |  disclaimers apply.
-----------------------------------------------------------------------------