Date: Wed, 7 Oct 1998 08:37:01 -0700 (PDT) From: Dan Busarow <dan@dpcsys.com> To: "Jeffrey J. Mountin" <jeff-ml@mountin.net> Cc: freebsd-security@FreeBSD.ORG Subject: Re: The necessary steps for logging (the problem is fixed) Message-ID: <Pine.BSF.3.96.981007082527.20457A-100000@java.dpcsys.com> In-Reply-To: <3.0.3.32.19981006205648.006e987c@207.227.119.2>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 6 Oct 1998, Jeffrey J. Mountin wrote: > 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. No, I'm refering to crontab(5)'s similarity to syslog.conf in that the last field of both can legally contain spaces. If any of the fields to the left of those fields could also contain spaces then spaces could *not* be used as a delimiter. Since in crontab(5) this is obviously not the case crontab(1)'s mixing of space and tab is fine. I'm asking if anyone has a working syslog.conf that uses spaces on the LHS. The docs don't support this but the code looks like it may. So to prevent the meltdown of previously working syslog.conf files this possability should be looked at. Dan -- Dan Busarow 949 443 4172 Dana Point Communications, a California corporation dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 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?Pine.BSF.3.96.981007082527.20457A-100000>