From owner-freebsd-bugs Tue Jan 29 4: 0: 8 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A429237B400 for ; Tue, 29 Jan 2002 04:00:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0TC03G71351; Tue, 29 Jan 2002 04:00:03 -0800 (PST) (envelope-from gnats) Date: Tue, 29 Jan 2002 04:00:03 -0800 (PST) Message-Id: <200201291200.g0TC03G71351@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: bin/32420: syslogd accumulates "repeated" messages when piping to programs when the program may want to take immediate action Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/32420; it has been noted by GNATS. From: Sheldon Hearn To: Archie Cobbs Cc: bug-followup@freebsd.org Subject: Re: bin/32420: syslogd accumulates "repeated" messages when piping to programs when the program may want to take immediate action Date: Tue, 29 Jan 2002 13:57:14 +0200 On Fri, 04 Jan 2002 23:50:01 PST, Archie Cobbs wrote: > Here's a candidate patch. Hi Archie, Sorry to come in late like this, but you moved pretty quickly on this one. :-) Your patch provides an all or nothing solution. What about systems that have syslogd pipe recipients, some of which are programmed to deal with aggregated messages and some of which are not? Wouldn't it be better to extend the ssylog.conf language so that the operator can choose _which_ pipe recipients should receive unaggregated messages? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message