From owner-freebsd-current Mon Jun 1 13:30:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26219 for freebsd-current-outgoing; Mon, 1 Jun 1998 13:30:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26143 for ; Mon, 1 Jun 1998 13:30:28 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.8/8.8.8) with ESMTP id VAA08511; Mon, 1 Jun 1998 21:30:17 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <35730F59.510D55FB@tdx.co.uk> Date: Mon, 01 Jun 1998 21:30:17 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: Mikhail Teterin CC: current@FreeBSD.ORG, toasty@home.dragondata.com Subject: Re: NFS discovery References: <199806011751.NAA29921@xxx.video-collage.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin wrote: > NFS hung ups are a strange topic, in my experience. People agree > that they are "bad", but one is not supposed to complain about > them... I remember having a long conversation with a friend a few years back (can I get any more vague?) - Where he was praising NFS's ability to crash - as it assures that say your running a program on a remote system, it will either run to completion - or hang if the server dies... This I presume works on the assumption that it helps somehow to have a client that's 'hung' in mid-air (i.e. at least you know if failed) rather than risking any corruption that might have been caused by the server disappearing for a while... I think you can change this behaviour - have a look at the man page for 'mount_nfs' - in particular things like the '-i' option & 'soft' mounting etc... Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message