freebsd-skq/usr.sbin/cron/lib/Makefile

# $FreeBSD$

LIB=	cron
INTERNALLIB=
SRCS= entry.c env.c misc.c

WARNS?=	3

CFLAGS+= -I${.CURDIR}/../cron
CFLAGS+= -DLOGIN_CAP -DPAM

.include <bsd.lib.mk>
Perform a major cleanup of the usr.sbin Makefiles. These are not perfectly in agreement with each other style-wise, but they are orders of orders of magnitude more consistent style-wise than before. 2001-07-20 06:20:32 +00:00			`# $FreeBSD$`
Paul Vixie's cron, version 3.0. Munged into bmake format. If this goes well, expect our two seperate directories for cron and crontab to go away shortly. Submitted by: jkh 1994-08-27 13:43:04 +00:00
Perform a major cleanup of the usr.sbin Makefiles. These are not perfectly in agreement with each other style-wise, but they are orders of orders of magnitude more consistent style-wise than before. 2001-07-20 06:20:32 +00:00			`LIB= cron`
For variables that are only checked with defined(), don't provide any fake value. 2004-10-24 15:33:08 +00:00			`INTERNALLIB=`
Perform a major cleanup of the usr.sbin Makefiles. These are not perfectly in agreement with each other style-wise, but they are orders of orders of magnitude more consistent style-wise than before. 2001-07-20 06:20:32 +00:00			`SRCS= entry.c env.c misc.c`

use WARNS?= instead of WARNS= MFC after: 3 days 2008-11-18 00:59:26 +00:00			`WARNS?= 3`
Make usr.sbin/cron/crontab and usr.sbin/cron/lib WARNS=3 clean Tested with: make universe MFC after: 3 days 2008-11-10 06:35:30 +00:00
Perform a major cleanup of the usr.sbin Makefiles. These are not perfectly in agreement with each other style-wise, but they are orders of orders of magnitude more consistent style-wise than before. 2001-07-20 06:20:32 +00:00			`CFLAGS+= -I${.CURDIR}/../cron`
Add PAM support to cron(8). Now cron(8) will skip commands scheduled by unavailable accounts, e.g., those locked, expired, not allowed in at the moment by nologin(5), or whatever, depending on cron's pam.conf(5). This applies to personal crontabs only, /etc/crontab is unaffected. In other words, now the account management policy will apply to commands scheduled by users via crontab(1) so that a user can no longer use cron(8) to set up a delayed backdoor and run commands during periods when the admin doesn't want him to. The PAM check is done just before running a command, not when loading a crontab, because accounts can get locked, expired, and re-enabled any time with no changes to their crontabs. E.g., imagine that you provide a system with payed access, or better a cluster of such systems with centralized account management via PAM. When a user pays for some days of access, you set his expire field respectively. If the account expires before its owner pays more, its crontab commands won't run until the next payment is made. Then it'll be enough to set the expire field in future for the commands to run again. And so on. Document this change in the cron(8) manpage, which includes adding a FILES section and touching the document date. X-Security: should benefit as users have access to cron(8) by default 2007-06-17 17:25:53 +00:00			`CFLAGS+= -DLOGIN_CAP -DPAM`
Paul Vixie's cron, version 3.0. Munged into bmake format. If this goes well, expect our two seperate directories for cron and crontab to go away shortly. Submitted by: jkh 1994-08-27 13:43:04 +00:00
			`.include <bsd.lib.mk>`