From: Jun T <firstname.lastname@example.org>
Subject: Re: Hang in E01 due to zpty on OpenBSD
Date: Fri, 8 Apr 2022 16:51:53 +0900 [thread overview]
Message-ID: <33F05F6B-F2BE-4EB0-A825-D5B549A435EF@kba.biglobe.ne.jp> (raw)
> 2022/04/07 13:52, Matthew Martin <email@example.com> wrote:
> I was thinking I'd wait until after the release and put the patch in the
> OpenBSD port until the next release. That way things are fixed with no
> need to rush.
OK, but for the next release:
I tried openpty() on Fedora-35 but it didn't work (W02jobs hangs).
posix_openpt() does not work on OpenBSD.
I can't think of any simple way to decide which of them to use
other than using OS test.
# or maybe we need to make zpty more robust?, but how?
next prev parent reply other threads:[~2022-04-08 7:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 21:42 Matthew Martin
2022-04-04 1:04 ` Bart Schaefer
2022-04-04 2:34 ` Matthew Martin
2022-04-04 3:49 ` Matthew Martin
2022-04-04 8:34 ` Jun T
2022-04-04 11:21 ` Mikael Magnusson
2022-04-04 13:16 ` Matthew Martin
2022-04-06 5:48 ` Jun T
2022-04-06 12:53 ` Matthew Martin
2022-04-06 20:12 ` Bart Schaefer
2022-04-07 3:47 ` Jun T
2022-04-07 4:52 ` Matthew Martin
2022-04-08 7:51 ` Jun T [this message]
2022-04-04 2:39 ` Jun T
2022-04-04 2:51 ` Matthew Martin
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).