Home
last modified time | relevance | path

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

12

/netbsd-src/external/bsd/cron/dist/
H A DCONVERSION3 Conversion of BSD 4.[23] crontab files:
5 Edit your current crontab (/usr/lib/crontab) into little pieces, with each
14 Leave the original /usr/lib/crontab! This cron doesn't use it, so you may
20 I recommend /etc/crontab.src or /usr/adm/crontab.src.
22 'uucp's commands need their own file; how about /usr/lib/uucp/crontab.src?
23 'news' also, perhaps in /usr/lib/news/crontab.src...
26 (except you) where you put the crontab source files. The `crontab' command
28 after the user whose crontab it is. If you want to examine, replace, or
29 delete a crontab, the `crontab' command does all of those things. The
30 various `crontab.src' (my suggested name for them) files are just source
[all …]
H A DMakefile85 MANPAGES = bitstring.3 crontab.5 crontab.1 cron.8 putman.sh
88 SOURCES = cron.c crontab.c database.c do_command.c entry.c \
93 LINT_CRONTAB = crontab.c misc.c entry.c env.c
96 CRONTAB_OBJ = crontab.o misc.o entry.o env.o pw_dup.o closeall.o
98 all : cron crontab
109 crontab : $(CRONTAB_OBJ) target
110 $(CC) $(LDFLAGS) -o crontab $(CRONTAB_OBJ) $(LIBS)
114 $(INSTALL) -c -m 4111 -o root -s crontab $(DESTBIN)/
117 sh putman.sh crontab.1 $(DESTMAN)
119 sh putman.sh crontab.5 $(DESTMAN)
[all …]
H A DFEATURES5 -- Environment variables can be set in each crontab. SHELL, USER,
7 USER can be changed in the crontab. PATH is especially useful to
28 person that cron mails the output of commands in that crontab. This is
44 -- Each user gets their own crontab file. This is a win over BSD 4.2,
45 where only root has one, and over BSD 4.3, where they made the crontab
47 uid's, root is still the only one who can edit the crontab file. This
50 -- The 'crontab' command is loosely compatible with SysV, but has more
51 options which just generally make more sense. Running crontab with
54 -- Comments and blank lines are allowed in the crontab file. Comments
58 -- (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 DREADME36 their own crontab file (all crontab files are stored in a read-protected
38 'at'; you can continue to run 'atrun' from the crontab as you have been
43 "crontab" command (which installs crontabs). It hasn't been tested on
60 build new crontabs using /usr/lib/{crontab,crontab.local}
61 (either put them all in "root"'s crontab, or divide it up
67 watch it. test it with 'crontab -r' and watch the daemon track your
H A DCHANGES27 The crontab command now conforms to POSIX 1003.2. This means that when you
28 install it, if you have any "crontab" command lines floating around in shell
36 is the ability to read in an /etc/crontab file which has an extra field in
38 name, and it permits the /etc/crontab command to contain commands which are
39 to be run by any user on the system. /etc/crontab is not "installed" via
40 the crontab(1) command; it is automatically read at startup time and it will
43 I also added a "-e" option to crontab(1). Nine people also sent me diffs
61 system, "crontab -u USER -d" will not work. My solution is to suggest to
63 user's crontab file if any. From cron's point of view, usernames can never
120 nasty security hole in "crontab -r". 'Nuff said.
[all …]
H A Duser.c42 for (e = u->crontab; e != NULL; e = ne) { in free_user()
76 u->crontab = NULL; in load_user()
99 e->next = u->crontab; in load_user()
100 u->crontab = e; in load_user()
H A DMAIL32 We have a lot of lines in our crontab of the form
115 of finding out why my crontab entry did not work.
121 particular crontab file if a command generates any output on stdout
137 write to their own crontab files). I'll add '-' (read stdin)
138 to the crontab installer program to facilitate this. >>
152 execution around, and purge it when the crontab was overwritten.
163 describe this by example. Say I have the following line in my crontab
194 in a crontab entry. I'd assumed that it was
220 user has their own crontab file; and something intelligent would
266 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
H A Dstructs.h54 entry *crontab; /* this person's crontab */ member
H A Dcron.c259 for (e = u->crontab; e != NULL; e = e->next) { in run_reboot_jobs()
393 for (e = u->crontab; e != NULL; e = e->next) { in find_jobs()
/netbsd-src/external/gpl3/gcc/dist/maintainer-scripts/
H A DChangeLog19 * crontab: Stop doing gcc-8 snapshots.
23 * crontab: Snapshots from trunk are now GCC 12 related.
88 * crontab: Snapshots from trunk are now GCC 11 related.
106 * crontab: Use update_web_docs_libstdcxx_git.
112 * crontab: Use update_web_docs_svn.
117 * crontab: Update gcc_release calls.
123 * crontab: Use update_version_git.
135 * crontab: Disable snapshots from gcc-7-branch.
144 * crontab: Snapshots from trunk are now GCC 10 related.
158 * crontab: Remove gcc-6-branch entry.
[all …]
/netbsd-src/external/bsd/cron/bin/crontab/
H A DMakefile6 PROG= crontab
7 SRCS= crontab.c misc.c entry.c env.c pw_dup.c closeall.c
12 MAN= crontab.1 crontab.5
/netbsd-src/etc/
H A Dcrontab1 # $NetBSD: crontab,v 1.16 2020/03/29 06:44:16 kim Exp $
3 # /var/cron/tabs/root - root's crontab for NetBSD
/netbsd-src/external/bsd/cron/bin/
H A DMakefile3 SUBDIR= cron crontab
/netbsd-src/external/gpl3/binutils.old/dist/binutils/
H A DREADME-how-to-make-a-release66 6. Update "BINUTILS_BRANCH" in gdbadmin's crontab:
70 $ cd crontab
71 $ vi crontab
73 $ cvs ci crontab
74 $ crontab crontab
/netbsd-src/share/doc/smm/01.setup/
H A Dspell.ok247 crontab
248 crontab.local
/netbsd-src/external/gpl3/binutils/dist/binutils/
H A DREADME-how-to-make-a-release78 6. Update "BINUTILS_BRANCH" in gdbadmin's crontab:
82 $ cd crontab
83 $ vi crontab
85 $ cvs ci crontab
86 $ crontab crontab
/netbsd-src/distrib/evbsh3/rom/ramdiskcommon/
H A Dramdiskbin.conf38 progs compress crontab ctags cut dirname du env file find finger from fsplit
/netbsd-src/games/fortune/datfiles/
H A Dnetbsd-tips133 file. As the superuser, use "crontab -l" to view it. To edit it,
134 use "crontab -e" (which defaults to using the vi(1) editor).
/netbsd-src/external/bsd/ntp/dist/scripts/update-leap/
H A Dupdate-leap-opts.def140 For cron-friendly behavior, define CRONJOB=1 in the crontab.
/netbsd-src/usr.bin/crunch/examples/
H A Dreally-big.conf41 progs cksum cmp col colcrt colrm column comm compress crontab ctags cut
/netbsd-src/usr.bin/spell/spell/
H A Dspecial.netbsd187 crontab
/netbsd-src/usr.sbin/makemandb/
H A Dnostem.txt610 crontab
/netbsd-src/external/bsd/nsd/dist/doc/
H A DREADME97 Step 11: If desired add 'nsd-control write' to your superuser crontab to

12