Date: Mon, 1 Nov 2004 16:19:55 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Mark Linimon <linimon@FreeBSD.org> Cc: freebsd-standards@FreeBSD.org Subject: Re: kern/72394: [PATCH] syslog is not thread-safe Message-ID: <20041101221955.GA55850@dan.emsphone.com> In-Reply-To: <200410300716.i9U7Gi48004946@freefall.freebsd.org> References: <200410300716.i9U7Gi48004946@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Oct 30), Mark Linimon said: > Synopsis: [PATCH] syslog is not thread-safe > > Responsible-Changed-From-To: freebsd-standards->freebsd-bugs > Responsible-Changed-By: linimon > Responsible-Changed-When: Sat Oct 30 07:15:43 GMT 2004 > Responsible-Changed-Why: > This sounds more like a kern bug than something for the standards folks. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=72394 Well, I guess the "unp_connect" message is a kernel bug, but that's a very minor part of the PR, and is marked with an "XXXRW: Temporary debugging printf" comment anyway. The larger issue is the lack of locking in the syslog family of libc functions, which POSIX requires. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041101221955.GA55850>