Searched refs:atrun (Results 1 – 10 of 10) sorted by path
/dragonfly/etc/ |
H A D | Makefile | 194 .for pamconf in README convert.sh atrun cron passwd su system
|
H A D | crontab | 10 */5 * * * * root /usr/libexec/atrun
|
/dragonfly/etc/pam.d/ |
H A D | Makefile | 5 atrun \
|
H A D | atrun | 2 # $FreeBSD: src/etc/pam.d/atrun,v 1.1 2007/06/15 12:02:16 yar Exp $ 4 # PAM configuration for the "atrun" service 7 # Note well: enabling pam_nologin for atrun will currently result
|
/dragonfly/libexec/ |
H A D | Makefile | 4 SUBDIR= atrun \
|
/dragonfly/libexec/atrun/ |
H A D | LEGAL | 1 # $FreeBSD: src/libexec/atrun/LEGAL,v 1.5 1999/08/28 00:09:11 peter Exp $ 2 # $DragonFly: src/libexec/atrun/LEGAL,v 1.2 2003/06/17 04:27:07 dillon Exp $
|
H A D | Makefile | 7 PROG= atrun 8 SRCS= atrun.c gloadavg.c 9 MAN= atrun.8
|
H A D | atrun.c | 82 static const char * const atrun = "atrun"; /* service name for syslog etc. */ variable 169 pam_err = pam_start(atrun, pentry->pw_name, &pamc, &pamh); in run_file() 456 openlog(atrun, LOG_PID, LOG_CRON); in main()
|
/dragonfly/usr.sbin/cron/doc/ |
H A D | MAIL | 264 2) At is integrated into the cron. Instead of atrun to scan the 271 'at', I use 'atrun' the same way the current BSD cron does. My
|
H A D | README | 31 'at'; you can continue to run 'atrun' from the crontab as you have been 32 doing. If you don't have atrun (i.e., System V) you are in trouble.
|