From: Florian Weimer <fw@deneb.enyo.de>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org, gam3@acm.org
Subject: Re: Problems with NFS exports
Date: Wed, 07 Aug 2002 13:51:22 +0200 [thread overview]
Message-ID: <87d6surio5.fsf@deneb.enyo.de> (raw)
In-Reply-To: <15697.511.36832.939913@notabene.cse.unsw.edu.au> (Neil Brown's message of "Wed, 7 Aug 2002 21:18:23 +1000")
Neil Brown <neilb@cse.unsw.edu.au> writes:
>> > And "BUSY" probably isn't correct ....
>>
>> Why not? The ressource (the directory tree) is already being used, and
>> therefore the export fails.
>
> I guess... I just feel it isn't really clear what it is that is
> 'busy'.
And it implies that it is just a temporary error condition, not a
configuration issue.
Maybe EEXIST is better?
prev parent reply other threads:[~2002-08-07 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 15:49 Problems with NFS exports Florian Weimer
2002-08-07 9:25 ` Florian Weimer
2002-08-07 10:40 ` Neil Brown
2002-08-07 11:13 ` Florian Weimer
2002-08-07 11:18 ` Neil Brown
2002-08-07 11:51 ` Florian Weimer [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=87d6surio5.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=gam3@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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