From owner-freebsd-current Tue Jan 4 8:56: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 723FB14DF3 for ; Tue, 4 Jan 2000 08:55:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA23681; Tue, 4 Jan 2000 08:55:55 -0800 (PST) (envelope-from dillon) Date: Tue, 4 Jan 2000 08:55:55 -0800 (PST) From: Matthew Dillon Message-Id: <200001041655.IAA23681@apollo.backplane.com> To: Phil Regnauld Cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS Race References: <20000104123804.23965@ns.int.ftf.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Just saw this passing on the console while compiling teTeX on an NFS :mounted dir: : :NFS append race @0:19 :NFS append race @0:135 :NFS append race @0:60 :NFS append race @0:102 :NFS append race @0:60 :NFS append race @0:12 :NFS append race @0:24 :NFS append race @0:66 :NFS append race @0:512 :NFS append race @0:958 : :What does that mean ? A few more popped up while I type this. This is catching a situation and printing a debug message for it. The problem existed previously but there was no debug message being printed for it before. It is probably harmless in the case of your compile. There were a bunch of situations that could cause this, including an append race for which the debug message was named after. The append race is now fixed but there are still a few situations that can cause this to occur. I will attempt to reproduce the problem by compiling up the teTeX port over a RW NFS mount. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message