From: Jim Rees <rees@umich.edu>
To: 宋哲 <songzhe@cintel.net.cn>
Cc: "SteveD@redhat.com" <SteveD@redhat.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Re: does nfs-util have a api-manual?
Date: Wed, 8 Jun 2011 22:05:33 -0400 [thread overview]
Message-ID: <20110609020533.GA26285@merit.edu> (raw)
In-Reply-To: <777962.29188.qm@web15806.mail.cnb.yahoo.com>
宋哲 wrote:
I have wrote a server application that record audio files to a nfs
directory, and I write to the directory just like it is a local disk.
But when some error occurs with the nfs-connection, the "write"
operation is just hanged up and does not return any errors, so I want to
use nfs-utils, and I think I can handle the error above with the tools.
But I almost know nothing about nfs-utils. Can you help me?
I don't think you need nfs-utils. The write() system call will hang
indefinitely if there is a problem with the mount. If you want it to fail
when the server goes away, you need a soft mount, and adjust the timeo and
retrans mount options to suit. See mount.nfs(8) and nfs(5).
prev parent reply other threads:[~2011-06-09 2:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 1:19 Re: does nfs-util have a api-manual? 宋哲
2011-06-09 2:05 ` Jim Rees [this message]
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=20110609020533.GA26285@merit.edu \
--to=rees@umich.edu \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=songzhe@cintel.net.cn \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox