xref: /dflybsd-src/usr.sbin/cron/doc/README (revision 86d7f5d305c6adaa56ff4582ece9859d73106103)
186d7f5d3SJohn Marino#/* Copyright 1988,1990,1993 by Paul Vixie
286d7f5d3SJohn Marino# * All rights reserved
386d7f5d3SJohn Marino# *
486d7f5d3SJohn Marino# * Distribute freely, except: don't remove my name from the source or
586d7f5d3SJohn Marino# * documentation (don't take credit for my work), mark your changes (don't
686d7f5d3SJohn Marino# * get me blamed for your possible bugs), don't alter or remove this
786d7f5d3SJohn Marino# * notice.  May be sold if buildable source is provided to buyer.  No
886d7f5d3SJohn Marino# * warrantee of any kind, express or implied, is included with this
986d7f5d3SJohn Marino# * software; use at your own risk, responsibility for damages (if any) to
1086d7f5d3SJohn Marino# * anyone resulting from the use of this software rests entirely with the
1186d7f5d3SJohn Marino# * user.
1286d7f5d3SJohn Marino# *
1386d7f5d3SJohn Marino# * Send bug reports, bug fixes, enhancements, requests, flames, etc., and
1486d7f5d3SJohn Marino# * I'll try to keep a version up to date.  I can be reached as follows:
1586d7f5d3SJohn Marino# * Paul Vixie          <paul@vix.com>          uunet!decwrl!vixie!paul
1686d7f5d3SJohn Marino# */
1786d7f5d3SJohn Marino
1886d7f5d3SJohn MarinoVixie Cron V3.0
1986d7f5d3SJohn MarinoDecember 27, 1993
2086d7f5d3SJohn Marino[V2.2 was some time in 1992]
2186d7f5d3SJohn Marino[V2.1 was May 29, 1991]
2286d7f5d3SJohn Marino[V2.0 was July 5, 1990]
2386d7f5d3SJohn Marino[V2.0-beta was December 9, 1988]
2486d7f5d3SJohn Marino[V1.0 was May 6, 1987]
2586d7f5d3SJohn MarinoPaul Vixie
2686d7f5d3SJohn Marino
2786d7f5d3SJohn MarinoThis is a version of 'cron' that is known to run on BSD 4.[23] systems.  It
2886d7f5d3SJohn Marinois functionally based on the SysV cron, which means that each user can have
2986d7f5d3SJohn Marinotheir own crontab file (all crontab files are stored in a read-protected
3086d7f5d3SJohn Marinodirectory, usually /var/cron/tabs).  No direct support is provided for
3186d7f5d3SJohn Marino'at'; you can continue to run 'atrun' from the crontab as you have been
3286d7f5d3SJohn Marinodoing.  If you don't have atrun (i.e., System V) you are in trouble.
3386d7f5d3SJohn Marino
3486d7f5d3SJohn MarinoA messages is logged each time a command is executed; also, the files
3586d7f5d3SJohn Marino"allow" and "deny" in /var/cron can be used to control access to the
3686d7f5d3SJohn Marino"crontab" command (which installs crontabs).  It hasn't been tested on
3786d7f5d3SJohn MarinoSysV, although some effort has gone into making the port an easy one.
3886d7f5d3SJohn Marino
3986d7f5d3SJohn MarinoThis is more or less the copyright that USENET contributed software usually
4086d7f5d3SJohn Marinohas.  Since ATT couldn't use this version if they had to freely distribute
4186d7f5d3SJohn Marinosource, and since I'd love to see them use it, I'll offer some rediculously
4286d7f5d3SJohn Marinolow license fee just to have them take it.  In the unlikely event that they
4386d7f5d3SJohn Marinodo this, I will continue to support and distribute the pseudo-PD version, so
4486d7f5d3SJohn Marinoplease, don't flame me for wanting my work to see a wider distribution.
4586d7f5d3SJohn Marino
4686d7f5d3SJohn MarinoTo use this: Sorry, folks, there is no cutesy 'Configure' script.  You'll
4786d7f5d3SJohn Marinohave to go edit a couple of files... So, here's the checklist:
4886d7f5d3SJohn Marino
4986d7f5d3SJohn Marino	Read all the FEATURES, INSTALL, and CONVERSION files
5086d7f5d3SJohn Marino	Edit config.h
5186d7f5d3SJohn Marino	Edit Makefile
5286d7f5d3SJohn Marino		(both of these files have instructions inside; note that
5386d7f5d3SJohn Marino		 some things in config.h are definable in Makefile and are
5486d7f5d3SJohn Marino		 therefore surrounded by #ifndef...#endif)
5586d7f5d3SJohn Marino	'make'
5686d7f5d3SJohn Marino	'su' and 'make install'
5786d7f5d3SJohn Marino		(you may have to install the man pages by hand)
5886d7f5d3SJohn Marino	kill your existing cron process
5986d7f5d3SJohn Marino		(actually you can run your existing cron if you want, but why?)
6086d7f5d3SJohn Marino	build new crontabs using /usr/lib/{crontab,crontab.local}
6186d7f5d3SJohn Marino		(either put them all in "root"'s crontab, or divide it up
6286d7f5d3SJohn Marino		 and rip out all the 'su' commands, collapse the lengthy
6386d7f5d3SJohn Marino		 lists into ranges with steps -- basically, this step is
6486d7f5d3SJohn Marino		 as much work as you want to make it)
6586d7f5d3SJohn Marino	start up the new cron
6686d7f5d3SJohn Marino		(must be done as root)
6786d7f5d3SJohn Marino	watch it. test it with 'crontab -r' and watch the daemon track your
6886d7f5d3SJohn Marino		changes.
6986d7f5d3SJohn Marino	if you like it, change your /etc/{rc,rc.local} to use it instead of
7086d7f5d3SJohn Marino		the old one.
7186d7f5d3SJohn Marino
7286d7f5d3SJohn Marino$FreeBSD: src/usr.sbin/cron/doc/README,v 1.4 1999/08/28 01:15:53 peter Exp $
7386d7f5d3SJohn Marino$DragonFly: src/usr.sbin/cron/doc/README,v 1.2 2003/06/17 04:29:53 dillon Exp $
74