From owner-freebsd-arch Sat Feb 15 1: 9:41 2003 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D92C337B401 for ; Sat, 15 Feb 2003 01:09:39 -0800 (PST) Received: from smtp-relay.omnis.com (smtp-relay.omnis.com [216.239.128.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6635D43FB1 for ; Sat, 15 Feb 2003 01:09:39 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.homeunix.net (66-75-151-22.san.rr.com [66.75.151.22]) by smtp-relay.omnis.com (Postfix) with ESMTP id 5A56A43028; Sat, 15 Feb 2003 01:09:38 -0800 (PST) From: Wes Peters Organization: Softweyr To: Garance A Drosihn , Terry Lambert , Gordon Tetlow Subject: Re: syslog.conf syntax change (multiple program/host specifications) Date: Sat, 15 Feb 2003 09:09:38 +0000 User-Agent: KMail/1.5 Cc: arch@FreeBSD.ORG References: <20030210114930.GB90800@melusine.cuivre.fr.eu.org> <3E4D7C2B.DDFC9DBE@mindspring.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200302150909.38103.wes@softweyr.com> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Saturday 15 February 2003 03:44, Garance A Drosihn wrote: > At 3:30 PM -0800 2/14/03, Terry Lambert wrote: > >Gordon Tetlow wrote: > >> From newsyslog(8): > > > -F Force newsyslog to trim the logs, even if the trim > > > conditions have not been met. This option is useful > > > for diagnosing system problems by providing you with > > > fresh logs that contain only the problems. > > > >Not really useful. > > > >For example, we had a system where cron would occasionally die, > > Note that what we are saying is that syslog would execute > newsyslog, at the moment syslog notes the logfile has grown > too large. Newsyslog would be told to "rotate this file now". > So, it wouldn't matter if cron dies. And the log would be > rotated right after the first syslog write which caused the > file to pass the size limit. Yes, it's important to keep in mind the desired change that caused this discussion in the first place. ;^) > I still have some message squirrelled away where you describe > this problem. I do agree this would be good to fix. It seems > to me that would be separate from the Wes's syslog change. Ie, > it's good to fix this whether or not Wes's change goes in, and > it's good for Wes's change to go in whether or not this is fixed. Yes, there's a very loose coupling between the two. I suppose it would be best to fix that while we're dorking around with newsyslog, but the solutions are going after the same end via two different paths: the syslog.conf change prevents it from happening and the newsyslog change fixes it after it's happened and crashed things. > >I would really object to rolling this same thing into syslog, > >without fixing this first. > > Some people talked about (basically) moving all of newsyslog > functions into syslog, but I don't think we are heading that > way. We're now just talking about having syslog run newsyslog > on a specific logfile. Or some very simple rolling behavior. If you need the full function- ality of newsyslog, it awaits your log-rolling pleasure. If your needs (or capacity) are more limited, I'd like syslogd to handle that itself. -- Where am I, and what am I doing in this handbasket? Wes Peters wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message