NetBSD/usr.sbin/cron/Makefile

#	$NetBSD: Makefile,v 1.11 2005/03/16 02:53:55 xtraeme Exp $

PROG=	cron
SRCS=	cron.c database.c do_command.c entry.c env.c job.c \
	misc.c popen.c user.c
CPPFLAGS+=-I${.CURDIR} -DLOGIN_CAP
LDADD+=-lutil
MAN=	cron.8

WARNS=  3

.include <bsd.prog.mk>
Kill __P(), use ANSI function declarations, constify; WARNS=3 2005-03-16 05:53:55 +03:00			`# $NetBSD: Makefile,v 1.11 2005/03/16 02:53:55 xtraeme Exp $`
Vixie Cron 3.0-prerelease, patch 9 1994-01-05 23:40:12 +03:00
Converted Makefile to use BSD make. 1994-01-05 23:57:27 +03:00			`PROG= cron`
RCSid police 1997-03-13 09:19:07 +03:00			`SRCS= cron.c database.c do_command.c entry.c env.c job.c \`
			`misc.c popen.c user.c`
PR/15142: Kevin P. Neal: cron does not pay attention to login_cap(3) I simplified the patch addressed certain security concerns. I only allowed setusercontext() to set resource limits/priority and umask, because these are the values that are relevant from login.conf. The rest of the settings (uid/gid/initgroups) should be done using e->uid and e->gid like they were before, not from: struct passwd *pwd = getpwnam(getenv("LOGNAME")); Finally login_cap's (path/env) are irrelevant in this context since we want to use our e->envp anyway to execute the command. 2003-03-15 00:56:07 +03:00			`CPPFLAGS+=-I${.CURDIR} -DLOGIN_CAP`
			`LDADD+=-lutil`
specify man pages the new way. 1994-12-22 14:32:57 +03:00			`MAN= cron.8`
Vixie Cron 3.0-prerelease, patch 9 1994-01-05 23:40:12 +03:00
Kill __P(), use ANSI function declarations, constify; WARNS=3 2005-03-16 05:53:55 +03:00			`WARNS= 3`

Converted Makefile to use BSD make. 1994-01-05 23:57:27 +03:00			`.include <bsd.prog.mk>`