From owner-freebsd-stable Fri May 17 11:51:35 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 683BE37B40C for ; Fri, 17 May 2002 11:51:29 -0700 (PDT) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020517185128.JEXL12519.rwcrmhc53.attbi.com@blossom.cjclark.org>; Fri, 17 May 2002 18:51:28 +0000 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.6) id g4HIpS466242; Fri, 17 May 2002 11:51:28 -0700 (PDT) (envelope-from crist.clark@attbi.com) X-Authentication-Warning: blossom.cjclark.org: cjc set sender to crist.clark@attbi.com using -f Date: Fri, 17 May 2002 11:51:27 -0700 From: "Crist J. Clark" To: Luigi Rizzo Cc: stable@FreeBSD.org Subject: Re: syslogd and inetd problems Message-ID: <20020517115127.B65921@blossom.cjclark.org> Reply-To: "Crist J. Clark" References: <20020517024345.A75815@iguana.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020517024345.A75815@iguana.icir.org>; from rizzo@icir.org on Fri, May 17, 2002 at 02:43:45AM -0700 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, May 17, 2002 at 02:43:45AM -0700, Luigi Rizzo wrote: > Hi, > recently I have seen the following problems with inetd and syslogd, > so was wondering if my diagnose is correct, other have seen them, > and how urgent is a fix. > > syslogd: > > + i am using syslogd to log to a remote system. From time to time, > the syslog daemon stops sending to the remote system, and I need > to restart it. Haven't traced the problem in detail, but it usually > happens across some network outage between the two. > > A high level inspection of the code in syslogd.c suggests that > the daemon closes the connection on a sendto failure, which is > probably not the smartest thing to do. At the very least, the > code should implement some recovery mechanism. Yes. I have patches someone sent me for this. IIRC, there is a PR attached. Before you start writing code, I'll try to forward the patches today or tomorrow. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message