From owner-freebsd-hackers Wed Jan 21 15:40:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11362 for hackers-outgoing; Wed, 21 Jan 1998 15:40:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tahiti.oss.uswest.net (tahiti.oss.uswest.net [204.147.85.151]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11349 for ; Wed, 21 Jan 1998 15:40:31 -0800 (PST) (envelope-from rantapaa@uswest.net) Received: (from rantapaa@localhost) by tahiti.oss.uswest.net (8.8.5/8.6.12) id RAA18505; Wed, 21 Jan 1998 17:30:42 -0600 (CST) Date: Wed, 21 Jan 1998 17:30:41 -0600 (CST) From: Erik E Rantapaa To: freebsd-hackers@FreeBSD.ORG Subject: syslogd, gethostby*() and signals Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk Just recently I've encountered several incidents where syslogd is dying right after it re-initializes due to a HUP signal. The core file suggests syslogd was in a gethostbyaddr() call in the cvthname() subroutine at the time of the signal. The HUP signal handler makes gethostbyname() calls. Is this a potential problem? I'm running 2.2.5-RELEASE . -- Erik Rantapaa rantapaa@uswest.net