Linux PARISC architecture development
 help / color / mirror / Atom feed
From: John Marvin <jsm@udlkern.fc.hp.com>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: EWOULDBLOCK vs. EAGAIN
Date: Tue, 22 Oct 2002 09:34:55 -0600 (MDT)	[thread overview]
Message-ID: <200210221534.JAA28679@udlkern.fc.hp.com> (raw)

OK, I should have checked the archives first. It looks like this issue
has already come up. In that case we fixed the app. But I'm not comfortable
with the fact that we are different from every other architecture here.

Yes, to be completely portable across other Unix flavors, you should
check for both EAGAIN and EWOULDBLOCK. But it would appear that
Gnu C library documentation says they should be the same, and they
ARE the same on all other Linux architectures. So, in my opinion,
we are broken, not the apps.

John

P.S. I know most of you don't care, but the broken app in this case is
telnetd. It drops connections if you blast too much to stdout.

             reply	other threads:[~2002-10-22 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22 15:34 John Marvin [this message]
2002-10-22 15:54 ` [parisc-linux] Re: EWOULDBLOCK vs. EAGAIN Randolph Chung
2002-10-24  9:56   ` GOTO Masanori
2002-10-22 15:58 ` John David Anglin

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=200210221534.JAA28679@udlkern.fc.hp.com \
    --to=jsm@udlkern.fc.hp.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    /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