From owner-freebsd-hackers Fri Oct 26 15:40: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from parhelion.firedrake.org (parhelion.firedrake.org [212.135.138.219]) by hub.freebsd.org (Postfix) with ESMTP id 6881A37B407 for ; Fri, 26 Oct 2001 15:39:59 -0700 (PDT) Received: from float by parhelion.firedrake.org with local (Exim 3.32 #1 (Debian)) id 15xFdt-0002aC-00 for ; Fri, 26 Oct 2001 23:39:57 +0100 Date: Fri, 26 Oct 2001 23:39:57 +0100 To: hackers@freebsd.org Subject: syslogd and kqueue Message-ID: <20011026233957.A9925@parhelion.firedrake.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23i From: void Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If syslogd used the kqueue interface, I believe it could open a new log file as soon as it was created, rather than waiting to receive a signal. Would this be worth doing, or would it be too big a divergence from the traditional behavior? -- Ben "An art scene of delight I created this to be ..." -- Sun Ra To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message