From owner-freebsd-hackers Wed Apr 18 18:56:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 05EF237B422 for ; Wed, 18 Apr 2001 18:56:19 -0700 (PDT) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id VAA46724 for hackers@freebsd.org; Wed, 18 Apr 2001 21:56:10 -0400 (EDT) (envelope-from mwlucas) Date: Wed, 18 Apr 2001 21:56:10 -0400 From: Michael Lucas To: hackers@freebsd.org Subject: thoughts on /etc/newsyslog.conf Message-ID: <20010418215610.A46691@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, In writing an article on syslogd and newsyslog, I've noticed something intensely annoying about newsyslog.conf. FreeBSD supports three different formats for dates in newsyslog.conf: raw hours since last rotation, ISO 8601, and FreeBSD-specific week-day-month. Wouldn't it make sense to standardize on one or the other of ISO8601 or W-D-M for the default newsyslog.conf? All of the existing entries could easily be expressed in W-D-M. Or is there some particular reason why we must use both formats in the default file? I'll be happy to document it if that's the case. I'd rather not try to justify using different formats to a new user without such a reason, however. As someone writing documentation, I'd prefer W-D-M since it's easier to explain. :) I will even volunteer patches to make it consistent in whatever form is chosen -- although I suspect one of you real hackers could do it with your eyes closed, I feel obliged to offer. Thanks, ==ml -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message