From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Danny Smith <dannys@cinesite.co.uk>
Cc: nfs <nfs@lists.sourceforge.net>,
Iain Irwin-Powell <Iain@cinesite.co.uk>
Subject: Re: NFSERR_EAGAIN
Date: 11 Jul 2003 00:41:13 +0200 [thread overview]
Message-ID: <shsbrw20zue.fsf@charged.uio.no> (raw)
In-Reply-To: <3F0DB088.303@cinesite.co.uk>
>>>>> " " == Danny Smith <dannys@cinesite.co.uk> writes:
> Looking through nfs2xdr.c and nfs.h and googling, it seems that
> error number 11 is not properly defined, but certainly seems to
> be in use by SGI. From nfs2xdr.c:
> { NFSERR_NXIO, ENXIO },
> /* { NFSERR_EAGAIN, EAGAIN }, */
> { NFSERR_ACCES, EACCES },
> (EAGAIN having value 11)
> Does anyone know much about the history of this? Was this
> removed in order to be RFC compliant, or is there a stronger
> motivation not to have this?
Why should we be supporting something which isn't documented in the RFCs?
What is this error anyway? Is it some SGI hack for emulating
NFS3ERR_JUKEBOX under NFSv2?
Cheers,
Trond
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-07-10 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 18:29 NFSERR_EAGAIN Danny Smith
2003-07-10 22:41 ` Trond Myklebust [this message]
2003-07-11 9:55 ` NFSERR_EAGAIN Danny Smith
2003-07-11 10:13 ` NFSERR_EAGAIN Trond Myklebust
2003-07-16 15:53 ` NFSERR_EAGAIN - resolved Danny Smith
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=shsbrw20zue.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=Iain@cinesite.co.uk \
--cc=dannys@cinesite.co.uk \
--cc=nfs@lists.sourceforge.net \
/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