From owner-freebsd-current Fri Apr 18 17:22:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA15925 for current-outgoing; Fri, 18 Apr 1997 17:22:40 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA15916 for ; Fri, 18 Apr 1997 17:22:36 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA03517; Fri, 18 Apr 1997 17:20:32 -0700 From: Terry Lambert Message-Id: <199704190020.RAA03517@phaeton.artisoft.com> Subject: Re: Speed deamons: How to build a build box? To: skynyrd@opus.cts.cwu.edu (Chris Timmons) Date: Fri, 18 Apr 1997 17:20:32 -0700 (MST) Cc: imp@village.org, current@freebsd.org In-Reply-To: from "Chris Timmons" at Apr 18, 97 12:52:00 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 3. Think carefully before using async mounts. > > 4. Think real hard about whether or not you want to async mount ... > got that fixit floppy handy? Actually... I found an issue with MNT_ASYNC in /sys/kern/vfs_syscalls.c in the fscync() code. Specifically, in the mount case, it doesn't wait for the write on the mount point being covered. I don't think this should be overridden in the mount point covering case, actually... it seems like it can lead to some ...problems. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.