From owner-freebsd-stable Tue Mar 23 14: 2: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from diamond.ripn.net (diamond.ripn.net [195.19.26.76]) by hub.freebsd.org (Postfix) with ESMTP id 0D88C14C56 for ; Tue, 23 Mar 1999 14:01:52 -0800 (PST) (envelope-from ilya@diamond.ripn.net) Received: (from ilya@localhost) by diamond.ripn.net (8.9.2/8.9.2) id BAA30776; Wed, 24 Mar 1999 01:01:16 +0300 (MSK) (envelope-from ilya) Message-Id: <199903232201.BAA30776@diamond.ripn.net> Subject: Re: Possible bug in syslog? In-Reply-To: from Mike Meyer at "Mar 22, 1999 1:47: 9 pm" To: mwm@phone.net (Mike Meyer) Date: Wed, 24 Mar 1999 01:01:15 +0300 (MSK) Cc: stable@FreeBSD.ORG From: Ilya Varlashkin X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Mike Meyer: > I noticed what I think is a problem. If your syslog is sending log > messages to a machine that you've shut down (for example, to do a > "make installworld" on it), it stops logging until you restart it. Is > this a bug? If so, I'll look into fixing it. If not, I can switch to > the daemontools port. it would be great if syslog'd be able to queue (most likely to disk) unsent messages and re-resend them as soon as loghost become available again. but it seems to be quite complex task. -- Ilya Varlashkin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message