Date: Mon, 11 Feb 2002 10:02:00 -0800 (PST) From: Brandon Poyner <bpoyner@thebiz.net> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/34839: syslogd fails to create additional log socket when socket already exists Message-ID: <200202111802.g1BI20j40188@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 34839 >Category: misc >Synopsis: syslogd fails to create additional log socket when socket already exists >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Feb 11 10:10:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Brandon Poyner >Release: 4.5 >Organization: BiznessOnline >Environment: FreeBSD sandbox.ct.thebiz.net 4.5-RELEASE FreeBSD 4.5-RELEASE #0: Mon Jan 28 14:31:56 GMT 2002 murray@builder.freebsdmall.com:/usr/src/sys/compile/GENERIC i386 >Description: If syslogd is run with -l flag to create additional log sockets it can under certain circumstances fail to unlink those log sockets before syslogd is started again. Syslogd will then report syslogd: cannot create /usr/jail/log: Address already in use >How-To-Repeat: If the server is power cycled (improper shutdown) syslogd will not get a signal to be killed and therefore not unlink() the additional log sockets. I have also seen this behavior during a 'sync;reboot' but I'm having trouble recreating that scenario. >Fix: Suggest that syslogd on startup automatically unlink() all sockets specified with -l as it currently does with /var/run/log, or a new flag to force the unlinking. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200202111802.g1BI20j40188>