summaryrefslogtreecommitdiff
path: root/usr.bin/crontab
AgeCommit message (Collapse)Author
2008-08-29Wrap compiler-specific flags with HAVE_GCC and HAVE_PCC as necessary. Add a ↵gmcgarry
few flags for PCC.
2007-05-28Add new Makefile knob, USE_FORT, which extends USE_SSP by turning on thetls
FORTIFY_SOURCE feature of libssp, thus checking the size of arguments to various string and memory copy and set functions (as well as a few system calls and other miscellany) where known at function entry. RedHat has evidently built all "core system packages" with this option for some time. This option should be used at the top of Makefiles (or Makefile.inc where this is used for subdirectories) but after any setting of LIB. This is only useful for userland code, and cannot be used in libc or in any code which includes the libc internals, because it overrides certain libc functions with macros. Some effort has been made to make USE_FORT=yes work correctly for a full-system build by having the bsd.sys.mk logic disable the feature where it should not be used (libc, libssp iteself, the kernel) but no attempt has been made to build the entire system with USE_FORT and doing so will doubtless expose numerous bugs and misfeatures. Adjust the system build so that all programs and libraries that are setuid, directly handle network data (including serial comm data), perform authentication, or appear likely to have (or have a history of having) data-driven bugs (e.g. file(1)) are built with USE_FORT=yes by default, with the exception of libc, which cannot use USE_FORT and thus uses only USE_SSP by default. Tested on i386 with no ill results; USE_FORT=no per-directory or in a system build will disable if desired.
2006-05-12apply -Wno-pointer-sign with GCC4.mrg
2002-09-18makefile delint. use NETBSDSRCDIR as appropriatelukem
1998-02-22WARNSifychristos
1997-10-24use CPPFLAGS instead of CFLAGSlukem
1997-10-19Define USE_UTIMES.mycroft
1997-10-19use WARNS=0 not WARNS?=0 to disable warningslukem
1997-10-18disable WARNS until usr.sbin cron is cleaned uplukem
1997-05-08Back out the .PATH.c changes. The .depend problem (and others)gwr
will be fixed using the new .NOPATH make feature instead.
1997-05-06Use .PATH.c: ...gwr
1997-01-09RCS ID policetls
1995-06-10Don't deny read permission on the executable.mycroft
1994-12-24don't need bsd.own.mk any more.cgd
1994-12-22specify man pages the new way.cgd
1994-12-20pull in bsd.own.mk by hand, early, so NOMAN= can be defined there.cgd
1994-02-10kill bogus install -d's, and clean slightlycgd
1994-01-20Don't compile with compat.c, since our C library allready has all thejtc
functions it provides.
1994-01-12note fact that 'cron' movedcgd
1994-01-05Hack to get both crontab.1 and crontab.5 manpages installed without havingjtc
to rename either file (before crontab.5 was renamed crontab.5.5).
1994-01-05Clean up deleted files.mycroft
1994-01-05Update for Vixie Cron 3.0jtc
1993-12-25fix previous security patchderaadt
1993-12-18plug security hole in "crontab -r".cgd
fix from Todd C. Miller <millert@cs.Colorado.EDU>
1993-12-07Eliminate some compiler warnings.mycroft
1993-11-10do the right thing with EDITOR and PATH. reported (with fix) bycgd
Roland McGrath <roland@frob.com>
1993-08-02Add RCS identifiers, remove some completely useless RCS logs and patchkitmycroft
headers, and a few other insignificant changes.
1993-07-18Use ${COPY}, not -c for install.mycroft
1993-05-28Clean up deleted files.mycroft
1993-05-28update for newest version of vixie's cron, as of May 27 1993cgd
1993-04-26Don't try to install man page if NOMAN set.mycroft
1993-03-28cleaned up such that it compiles quietlyglass
now installs with right permissions now installs both man pages properly
1993-03-21initial import of 386bsd-0.1 sourcescgd