Home
last modified time | relevance | path

Searched refs:crontab (Results 1 – 25 of 30) sorted by relevance

12

/freebsd/usr.sbin/cron/doc/
H A DCONVERSION2 Conversion of BSD 4.[23] crontab files:
4 Edit your current crontab (/usr/lib/crontab) into little pieces, with each
13 Leave the original /usr/lib/crontab! This cron doesn't use it, so you may
19 I recommend /etc/crontab.src or /usr/adm/crontab.src.
21 'uucp's commands need their own file; how about /usr/lib/uucp/crontab.src?
22 'news' also, perhaps in /usr/lib/news/crontab.src...
25 (except you) where you put the crontab source files. The `crontab' command
27 after the user whose crontab it is. If you want to examine, replace, or
28 delete a crontab, the `crontab' command does all of those things. The
29 various `crontab.src' (my suggested name for them) files are just source
[all …]
H A DMakefile.vixie83 MANPAGES = bitstring.3 crontab.5 crontab.1 cron.8 putman.sh
85 SOURCES = cron.c crontab.c database.c do_command.c entry.c \
90 LINT_CRONTAB = crontab.c misc.c entry.c env.c
93 CRONTAB_OBJ = crontab.o misc.o entry.o env.o
95 all : cron crontab
106 crontab : $(CRONTAB_OBJ)
107 $(CC) $(LDFLAGS) -o crontab $(CRONTAB_OBJ) $(LIBS)
111 $(INSTALL) -c -m 4111 -o root -s crontab $(DESTBIN)/
112 sh putman.sh crontab.1 $(DESTMAN)
114 sh putman.sh crontab.5 $(DESTMAN)
[all …]
H A DFEATURES4 -- Environment variables can be set in each crontab. SHELL, USER,
6 USER can be changed in the crontab. PATH is especially useful to
27 person that cron mails the output of commands in that crontab. This is
43 -- Each user gets their own crontab file. This is a win over BSD 4.2,
44 where only root has one, and over BSD 4.3, where they made the crontab
46 uid's, root is still the only one who can edit the crontab file. This
49 -- The 'crontab' command is loosely compatible with SysV, but has more
50 options which just generally make more sense. Running crontab with
53 -- Comments and blank lines are allowed in the crontab file. Comments
57 -- (big win) If the `crontab' command changes anything in any crontab,
[all …]
H A DINSTALL31 both the daemon and the `crontab' program will do this the first time they
59 Edit your /usr/lib/crontab file into little pieces -- see the CONVERSION file
62 Use the `crontab' command to install all the little pieces you just created.
65 crontab -u uucp -r /usr/lib/uucp/crontab.src
66 crontab -u news -r /usr/lib/news/crontab.src
67 crontab -u root -r /usr/adm/crontab.src
71 they are reinstalled with another `crontab -r' command. (2) The crontab
72 command will affect the crontab of the person using the command unless `-u
74 under most BSD's, `crontab' will still think of you as yourself even though
76 option stands for `replace'; check the man page for crontab(1) for other
H A DREADME32 their own crontab file (all crontab files are stored in a read-protected
34 'at'; you can continue to run 'atrun' from the crontab as you have been
39 "crontab" command (which installs crontabs). It hasn't been tested on
56 build new crontabs using /usr/lib/{crontab,crontab.local}
57 (either put them all in "root"'s crontab, or divide it up
63 watch it. test it with 'crontab -r' and watch the daemon track your
H A DCHANGES7 The crontab command now conforms to POSIX 1003.2. This means that when you
8 install it, if you have any "crontab" command lines floating around in shell
16 is the ability to read in an /etc/crontab file which has an extra field in
18 name, and it permits the /etc/crontab command to contain commands which are
19 to be run by any user on the system. /etc/crontab is not "installed" via
20 the crontab(1) command; it is automatically read at startup time and it will
23 I also added a "-e" option to crontab(1). Nine people also sent me diffs
41 system, "crontab -u USER -d" will not work. My solution is to suggest to
43 user's crontab file if any. From cron's point of view, usernames can never
100 nasty security hole in "crontab -r". 'Nuff said.
[all …]
H A DMAIL30 We have a lot of lines in our crontab of the form
113 of finding out why my crontab entry did not work.
119 particular crontab file if a command generates any output on stdout
135 write to their own crontab files). I'll add '-' (read stdin)
136 to the crontab installer program to facilitate this. >>
150 execution around, and purge it when the crontab was overwritten.
161 describe this by example. Say I have the following line in my crontab
192 in a crontab entry. I'd assumed that it was
218 user has their own crontab file; and something intelligent would
264 a crontab file to run them. This is considered a major win by all who
[all …]
H A DTHANKS25 -> crontab says the right thing if you do something you shouldn't do
26 -> crontab(5) man page is longer and more informative
/freebsd/usr.sbin/cron/crontab/
H A DMakefile4 PROG= crontab
5 MAN= crontab.1 crontab.5
/freebsd/usr.sbin/cron/cron/
H A Duser.c36 for (e = u->crontab; e != NULL; e = ne) { in free_user()
78 u->crontab = NULL; in load_user()
102 e->next = u->crontab; in load_user()
103 u->crontab = e; in load_user()
H A Dcron.c194 for (e = u->crontab; e != NULL; e = e->next) {
244 for (e = u->crontab; e != NULL; e = e->next) {
259 for (e = u->crontab; e != NULL; e = e->next) {
274 for (e = u->crontab; e != NULL; e = e->next) {
301 for (e = u->crontab; e != NULL; e = e->next) {
458 for (e = u->crontab; e != NULL; e = e->next) {
545 for (e = u->crontab; e != NULL; e = e->next) {
560 for (e = u->crontab; e != NULL; e = e->next) {
H A Dcrontab1 # /etc/crontab - root's crontab for FreeBSD
H A DMakefile2 CONFS= crontab
H A Dstructs.h70 entry *crontab; /* this person's crontab */ member
H A Ddatabase.c303 for (e = u->crontab; e != NULL; e = e->next) { in process_crontab()
/freebsd/sys/contrib/openzfs/.github/workflows/scripts/
H A Dqemu-5-setup.sh105 echo '*/5 * * * * /root/cronjob.sh' > crontab.txt
106 sudo crontab crontab.txt
107 rm crontab.txt
/freebsd/share/examples/etc/
H A DREADME.examples12 crontab - system scheduled command table (see crontab(5))
59 security - script run from crontab to do nightly security checks
/freebsd/usr.sbin/cron/
H A DMakefile1 SUBDIR= lib cron crontab
/freebsd/usr.bin/at/
H A Datrun5 # See crontab(5) for field format.
/freebsd/release/
H A DMakefile.firecracker51 sed -i '' -e '/periodic/s/^/#/' ${FCWDIR}/etc/crontab
/freebsd/share/doc/smm/01.setup/
H A Dspell.ok246 crontab
247 crontab.local
/freebsd/release/packages/
H A DMakefile.package40 cron_COMMENT= cron(8) and crontab(1)
41 cron_DESC= cron(8) and crontab(1)
/freebsd/release/tools/
H A Dgce.conf79 cat << EOF >> ${DESTDIR}/etc/crontab
/freebsd/contrib/openbsm/etc/
H A Daudit_event623 6148:AUE_crontab_create:crontab-crontab created:ad
624 6149:AUE_crontab_delete:crontab-crontab deleted:ad
625 6150:AUE_crontab_perm:crontab-permission:no
645 6170:AUE_crontab_mod:crontab-modify:ad
/freebsd/contrib/ntp/scripts/update-leap/
H A Dupdate-leap-opts.def140 For cron-friendly behavior, define CRONJOB=1 in the crontab.

12