Date: Tue, 06 Oct 1998 20:56:48 -0500 From: "Jeffrey J. Mountin" <jeff-ml@mountin.net> To: Dan Busarow <dan@dpcsys.com>, Studded <Studded@dal.net> Cc: freebsd-security@FreeBSD.ORG Subject: Re: The necessary steps for logging (the problem is fixed) Message-ID: <3.0.3.32.19981006205648.006e987c@207.227.119.2> In-Reply-To: <Pine.BSF.3.96.981006103009.16376H-100000@java.dpcsys.com> References: <361A4F37.141BAE11@dal.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:35 AM 10/6/98 -0700, Dan Busarow wrote: >Unless someone can demonstrate a valid use of spaces on the LHS >crontab style checking would work though. (spaces are only legal >in the last field of crontab as well) Huh? You are refering to the checking, but the original /etc/crontab's for 2.2.7 and the 9/30 beta are mostly spaces, but the do mix tabs and spaces on the LHS, assuming you are referring in this case to only the time/date fields. In 2.2.7 (v1.13) even has a tab between adjkerntz and the -a flag that the beta (v.1.18) did not. There was some other space/tab swapping between the 2, but crontab is _not_ consistant or mentioned clearly (at all) in the man pages. The important parts are almost identical. Jeez. Otherwise a warning for syslog would be good, but I've always used tabs for better clarity reading syslog.conf. Good time to make a decision for crontab or at least the file. ;) Jeff Mountin - Unix Systems TCP/IP networking jeff@mountin.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.3.32.19981006205648.006e987c>