Date: Thu, 22 Jan 1998 17:11:30 -0800 (PST) From: rantapaa@uswest.net To: freebsd-gnats-submit@FreeBSD.ORG Subject: bin/5548: syslogd core dumps when signaled Message-ID: <199801230111.RAA09992@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 5548 >Category: bin >Synopsis: syslogd core dumps when signaled >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 22 17:20:01 PST 1998 >Last-Modified: >Originator: Erik Rantapaa >Organization: US West !nteract >Release: 2.2.5-STABLE >Environment: FreeBSD phnxauth.phnx.uswest.net 2.2.5-RELEASE FreeBSD 2.2.5-RELEASE #0: Fri Oct 24 04:49:36 MST 1997 root@phnxauth.phnx.uswest.net:/usr/src/sys/compile/AUTH i386 >Description: If syslogd is HUP'ed while in the gethostbyaddr() routine in cvthname() it will core dump upon returning from the signal handler. Apparently this happens because the signal handler (the function init() in this case) calls gethostbyname() and I'm guessing that there is some common routine which is not re-entrant. One fix is to block SIGHUP around the gethostbyaddr() call in cvthname(). >How-To-Repeat: Launch syslogd, start up a process which sends syslog requests from various ip addresses. Start up another process which just signals the syslogd process very frequently. syslogd will die with in a minute or so. >Fix: See above. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801230111.RAA09992>