From owner-freebsd-hackers Mon Aug 21 22:29:04 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id WAA03738 for hackers-outgoing; Mon, 21 Aug 1995 22:29:04 -0700 Received: from hutcs.cs.hut.fi (hutcs.cs.hut.fi [130.233.192.2]) by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id WAA03732 for ; Mon, 21 Aug 1995 22:29:00 -0700 Received: from shadows.cs.hut.fi by hutcs.cs.hut.fi with SMTP id AA05419 (5.65c8/HUTCS-S 1.4 for ); Tue, 22 Aug 1995 08:17:50 +0300 Received: (hsu@localhost) by shadows.cs.hut.fi (8.6.10/8.6.10) id IAA01893; Tue, 22 Aug 1995 08:17:53 +0300 Date: Tue, 22 Aug 1995 08:17:53 +0300 Message-Id: <199508220517.IAA01893@shadows.cs.hut.fi> From: Heikki Suonsivu To: terry@cs.weber.edu (Terry Lambert) Cc: freebsd-hackers@freefall.FreeBSD.org In-Reply-To: terry@cs.weber.edu's message of 20 Aug 1995 22:43:41 +0300 Subject: Re: Making a FreeBSD NFS server Organization: Helsinki University of Technology, Otaniemi, Finland Sender: hackers-owner@FreeBSD.org Precedence: bulk Correct my previous post to say "don't enable async writes, ever, it's not worth it (unless you have a UPS on your server). It still could be fixed (-o async does not seem to do anything now). It is somewhat annoying to, say, copy a news file system to another disk. I couldn't care less if I would have to newfs the whole target in case of panic or power hick-up during the copy. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN