All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: Larry McVoy <lm@bitmover.com>
Cc: parisc-linux@lists.parisc-linux.org, phi@hpfrcu81.france.hp.com,
	dev@bitmover.com
Subject: Re: [parisc-linux] rlogin: connection closed (SOLUTION)
Date: Mon, 2 Dec 2002 20:56:57 -0800	[thread overview]
Message-ID: <20021203045657.GU21187@tausq.org> (raw)
In-Reply-To: <200212022154.gB2LsPc31908@work.bitmover.com>

In reference to a message from Larry McVoy, dated Dec 02:
> This fixes it.  Looks like a race, I wasn't inclined to dig further, this
> got me past the problem.  I suspect that parisc fork() runs parent/child
> in the opposite order from every other Unix and that causes a race but
> I have not looked.

Nah, this is not it. It's the problem with EAGAIN != EWOULDBLOCK on 
hppa-linux.

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

  reply	other threads:[~2002-12-03  4:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02 21:54 [parisc-linux] rlogin: connection closed (SOLUTION) Larry McVoy
2002-12-03  4:56 ` Randolph Chung [this message]
2002-12-03  5:00   ` Larry McVoy

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=20021203045657.GU21187@tausq.org \
    --to=randolph@tausq.org \
    --cc=dev@bitmover.com \
    --cc=lm@bitmover.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=phi@hpfrcu81.france.hp.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.