From owner-freebsd-bugs Tue Nov 9 2:50: 4 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A42DB14CF7 for ; Tue, 9 Nov 1999 02:50:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id CAA39867; Tue, 9 Nov 1999 02:50:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Tue, 9 Nov 1999 02:50:01 -0800 (PST) Message-Id: <199911091050.CAA39867@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: kern/14797: Serious locking problem in CURRENT Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/14797; it has been noted by GNATS. From: Sheldon Hearn To: vince@pele.WURLDLINK.NET Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/14797: Serious locking problem in CURRENT Date: Tue, 09 Nov 1999 12:45:36 +0200 On Mon, 08 Nov 1999 23:11:18 -1000, Vincent Poy wrote: > You can do a little test of the file locking, might be a bit tricky if > you have a busy system, but it would be interesting to see the result: > > Run sendmail with -bd -q1m Sendmail isn't a "little test" of anything. :-) There are discussions on the -current mailing list (which you should be reading if you're posting CURRENT problem reports) regarding file locking. I believe Brian Feldman fixed a locking problem over the week-end. You'd know this too if you followed your commit mail, eh? ;-) Please try kern_descrip.c rev 1.72 and see if it fixes whatever problem you're having. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message