Home
last modified time | relevance | path

Searched refs:cron (Results 1 – 25 of 59) sorted by relevance

123

/freebsd-14.2/usr.sbin/cron/doc/
H A DMakefile.vixie83 MANPAGES = bitstring.3 crontab.5 crontab.1 cron.8 putman.sh
84 HEADERS = bitstring.h cron.h config.h pathnames.h externs.h
85 SOURCES = cron.c crontab.c database.c do_command.c entry.c \
88 LINT_CRON = cron.c database.c user.c entry.c \
95 all : cron crontab
103 cron : $(CRON_OBJ)
104 $(CC) $(LDFLAGS) -o cron $(CRON_OBJ) $(LIBS)
110 $(INSTALL) -c -m 111 -o root -s cron $(DESTSBIN)/
113 sh putman.sh cron.8 $(DESTMAN)
116 clean :; rm -f *.o cron crontab a.out core tags *~ #*
[all …]
H A DMAIL13 every two hours. Current cron requires me to write
18 The time specification for my cron is as follows:
118 << My cron (and the SysV cron) will send mail to the owner of the
254 Oh, yeah - here are the extensions on my cron:
257 BSD cron.
263 directory along with users cron files, and cron fabricates a line from
278 << This means cron.allow and cron.deny. I plan to support them, as
338 2. A way to avoid logging stuff in /usr/lib/cron/log. I have a cron entry
386 children in the cron program itself? Our cron does this and it's the pits
413 a file /usr/spool/cron/POKECRON is created; next time the cron
[all …]
H A DCONVERSION6 but I'll get to that below. The biggest feature of this cron is that you
7 can move 'news' and 'uucp' cron commands into files owned and maintainable
9 of the cron commands. On 4.3, there's no need for the 'su' stuff since the
13 Leave the original /usr/lib/crontab! This cron doesn't use it, so you may
26 COPIES them into a protected directory (CRONDIR/SPOOL_DIR in cron.h), named
64 The application to the `news' cron commands (if any) is left for you to
68 user, put the cron commands into it, and install it using the `crontab'
74 There would still be advantages to this cron, mostly that you get mail if
75 there is any output from your cron commands.
77 One note about getting mail from cron: you will probably find, after you
[all …]
H A DFEATURES2 Features of Vixie's cron relative to BSD 4.[23] and SysV crons:
7 set there. TZ can be set, but cron ignores it other than passing
27 person that cron mails the output of commands in that crontab. This is
28 useful if you decide on BINMAIL when configuring cron.h, since binmail
47 feature mimics the SysV cron.
58 the 'cron' daemon will reload all the tables before running the
64 readable or writable except by 'crontab' or 'cron'. This is not a
79 this behaviour; it's how cron has always worked but the documentation
82 the various field-matches together. In that sense this cron may not
H A DREADME30 This is a version of 'cron' that is known to run on most systems. It
31 is functionally based on the SysV cron, which means that each user can have
33 directory, usually /var/cron/tabs). No direct support is provided for
38 "allow" and "deny" in /var/cron can be used to control access to the
54 kill your existing cron process
55 (actually you can run your existing cron if you want, but why?)
61 start up the new cron
H A DINSTALL30 You don't have to create the /var/cron or /var/cron/tabs directories, since
79 Kill your existing cron daemon -- do `ps aux' and look for /etc/cron.
82 /etc/cron. Comment it out and add a line to start the new cron daemon
83 -- usually /usr/local/etc/cron, unless you changed it in the Makefile.
85 Start up this cron daemon yourself as root. Just type /usr/local/etc/cron
H A DCHANGES14 the name of the cron daemon has changed from "crond" to "cron". This was
32 descriptors to pass information to subshells, and cron was causing them to
43 user's crontab file if any. From cron's point of view, usernames can never
68 comments in cron.h.
76 did send me smaller patches which appear to have cause cron to build and run
128 called POKECRON in /usr/spool/cron to tell it that it was time to re-read
141 16-Feb-88: added allow/deny, moved /usr/spool/cron/crontabs to
142 /usr/lib/cron/tabs. allow and deny are /usr/lib/cron/{allow,deny},
150 9-Dec-88: made it sync to :00 after the minute, makes cron predictable.
151 added logging to /var/cron/log.
H A DTHANKS4 Many people have contributed to cron. Many more than I can remember, in fact.
15 its brothers and sisters; he also sent some diffs that lead cron toward compil-
16 ability with System V, though without at(1) capabilities, this cron isn't going
H A DREADME.1ST2 remains faithful to the original 3.0 cron source from Paul Vixie, but
/freebsd-14.2/usr.sbin/cron/cron/
H A DMakefile3 PROG= cron
4 MAN= cron.8
5 SRCS= cron.c database.c do_command.c job.c user.c popen.c
9 LIBADD= cron pam util
H A DMakefile.depend11 usr.sbin/cron/lib \
/freebsd-14.2/usr.sbin/cron/lib/
H A DMakefile2 LIB= cron
8 CFLAGS+= -I${.CURDIR:H}/cron
/freebsd-14.2/usr.sbin/cron/crontab/
H A DMakefile12 CFLAGS+= -I${.CURDIR:H}/cron
14 LIBADD= cron md util
H A DMakefile.depend11 usr.sbin/cron/lib \
/freebsd-14.2/usr.sbin/syslogd/
H A Dsyslog.conf12 cron.* /var/log/cron
/freebsd-14.2/libexec/bootpd/
H A Dsyslog.conf17 daemon,syslog,lpr,news,uucp,cron.err /dev/console
21 daemon.notice;syslog,news,uucp,cron.err /var/adm/messages
/freebsd-14.2/usr.sbin/cron/
H A DMakefile2 SUBDIR= lib cron crontab
/freebsd-14.2/lib/libpam/pam.d/
H A Dcron3 # PAM configuration for the "cron" service
H A DMakefile10 cron \
/freebsd-14.2/usr.bin/at/
H A DMakefile5 CONFSDIR= /etc/cron.d
/freebsd-14.2/contrib/ntp/ntpdc/
H A Dntpdc.texi34 well. It can be run as an interactive command or from a cron job.
82 @code{cron} job to reset the local clock from a reliable server, like
/freebsd-14.2/contrib/libcbor/.github/workflows/
H A Dfuzz.yml4 - cron: '0 4 * * *'
/freebsd-14.2/usr.sbin/newsyslog/
H A Dnewsyslog.conf20 /var/log/cron 600 3 1000 * JC
/freebsd-14.2/contrib/libfido2/.github/workflows/
H A Dcodeql-analysis.yml17 - cron: '0 0 * * 0'
/freebsd-14.2/etc/mtree/
H A DBSD.root.dist48 cron.d

123