From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
To: nfs@lists.sourceforge.net
Cc: "Lever, Charles" <Charles.Lever@netapp.com>,
"'Scott Mcdermott'" <smcdermott@questra.com>
Subject: Re: Re: broken umount -f
Date: Wed, 15 Jan 2003 13:22:14 -0500 [thread overview]
Message-ID: <20030115132214.A13482@ti19> (raw)
In-Reply-To: <20030115130759.B11894@ti19>; from brugolsky@ytelemetry-investments.com on Wed, Jan 15, 2003 at 01:07:59PM -0500
[Sorry, for the resend; I broke my return address on the first try.]
On Wed, Jan 15, 2003 at 09:04:58AM -0800, Lever, Charles wrote:
> do you know what the risk of data corruption is when using "intr"?
> seems pretty low to me.
Any reason why we can't add a mount option that makes cl_intr only
effective for SIGKILL in sunrpc/clnt.c? (A general sigmask= option
doesn't seem immediately useful, unless there is some use for [T]STOP.)
Regards,
Bill Rugolsky
-------------------------------------------------------
This SF.NET email is sponsored by: A Thawte Code Signing Certificate
is essential in establishing user confidence by providing assurance of
authenticity and code integrity. Download our Free Code Signing guide:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0028en
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-01-15 18:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 17:04 Re: broken umount -f Lever, Charles
2003-01-15 17:23 ` Scott Mcdermott
[not found] ` <20030115130759.B11894@ti19>
2003-01-15 18:22 ` Bill Rugolsky Jr. [this message]
2003-01-15 18:24 ` Scott Mcdermott
2003-01-15 19:11 ` NFS problem: udp port nfs unreachable Cuenta de la lista de linux
2003-01-16 20:49 ` Re: broken umount -f Ion Badulescu
-- strict thread matches above, loose matches on Subject: below --
2003-01-16 19:45 Re: Broken " Cole, Timothy D.
2003-01-16 19:56 ` Scott Mcdermott
2003-01-15 19:59 Heflin, Roger A.
2003-01-16 3:37 ` Scott Mcdermott
2003-01-15 18:46 Re: broken " Cole, Timothy D.
2003-01-15 15:35 Murata, Dennis W (SAIC)
2003-01-15 14:45 Lever, Charles
2003-01-15 16:32 ` Scott Mcdermott
2003-01-14 19:49 Cole, Timothy D.
2003-01-14 19:36 Lever, Charles
2003-01-15 5:19 ` Scott Mcdermott
2003-01-15 5:21 ` Scott Mcdermott
2003-01-14 19:30 Cole, Timothy D.
2003-01-14 15:56 [NFS] " Lever, Charles
2003-01-14 17:07 ` Scott Mcdermott
2003-01-14 19:06 ` Trond Myklebust
2003-01-14 19:19 ` Scott Mcdermott
2003-01-14 19:32 ` Brian Tinsley
2003-01-14 19:35 ` Trond Myklebust
2003-01-14 22:17 ` Scott Mcdermott
2003-01-14 22:29 ` Steven N. Hirsch
2003-01-14 22:27 ` Steven N. Hirsch
2003-01-14 19:39 ` Benjamin LaHaise
2003-01-14 19:52 ` Trond Myklebust
2003-01-14 19:56 ` Benjamin LaHaise
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030115132214.A13482@ti19 \
--to=brugolsky@telemetry-investments.com \
--cc=Charles.Lever@netapp.com \
--cc=nfs@lists.sourceforge.net \
--cc=smcdermott@questra.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.