Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: prisma!berliner@uunet.uu.net (Brian Berliner)
Newsgroups: comp.sys.sun
Subject: Re: -intr mount option?
Keywords: SunOS
Message-ID: <3446@kalliope.rice.edu>
Date: 26 May 89 20:35:52 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 19
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 8, Issue 4, message 1 of 13

In Sun-Spots Digest v7n304, stanonik@nprdc.navy.mil (Ron Stanonik) asks:
> Is there ever a time when you wouldn't want to use the -intr mount option?
> That is, why isn't it the default?

I asked myself the exact same thing while doing the NFS port for Convex.
And in no way could I convince myself that it isn't what is always wanted
-- after all, I *did* interrupt the program to kill it, or have my signal
processed in some way!

So, in the Convex NFS distribution, -intr is the default, and it can be
disabled with the new -nointr option to mount.  Hard mounts without -intr
are too likely to burn people not really interested in the particular
mount doing a "df", or what not.

					Brian Berliner
					Prisma, Inc.
					berliner@prisma.com

Disclaimer: Convex is a previous employer and I do not claim to speak for them.