From: Russell King <rmk@arm.linux.org.uk>
To: Bernd Petrovitsch <bernd@gams.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: open("/dev/ttyS1", O_LARGEFILE) blocks
Date: Mon, 14 Oct 2002 12:52:06 +0100 [thread overview]
Message-ID: <20021014125206.A2902@flint.arm.linux.org.uk> (raw)
In-Reply-To: <2379.1034595547@frodo.gams.co.at>; from bernd@gams.at on Mon, Oct 14, 2002 at 01:39:07PM +0200
On Mon, Oct 14, 2002 at 01:39:07PM +0200, Bernd Petrovitsch wrote:
> Hi all!
>
> Is is normal/correct/intended that an open() of /dev/ttyS1 blocks?
> ---- snip ----
> {81}strace ./test-open /dev/ttyS0
> [...]
> open("/dev/ttyS0", O_RDONLY|O_NONBLOCK) = 3
> close(3) = 0
> open("/dev/ttyS0", O_RDONLY|O_NONBLOCK|O_LARGEFILE) = 3
> close(3) = 0
> open("/dev/ttyS0", O_RDONLY|O_LARGEFILE) = 3
> close(3) = 0
> _exit(0) = ?
> {82}strace ./test-open /dev/ttyS1
> [...]
> open("/dev/ttyS1", O_RDONLY|O_NONBLOCK) = 3
> close(3) = 0
> open("/dev/ttyS1", O_RDONLY|O_NONBLOCK|O_LARGEFILE) = 3
> close(3) = 0
> open("/dev/ttyS1", O_RDONLY|O_LARGEFILE <unfinished ...>
> {83}lsof /dev/ttyS0
> {84}lsof /dev/ttyS1
> {85}uname -a
> Linux xxx 2.4.20-pre10aa1 #6 Fri Oct 11 13:41:20 CEST 2002 i686 unknown
> ---- snip ----
>
> The second one was terminated with a Ctrl-C.
> Nothing was connected to none of the ports.
> Is there a reason that an open() on /dev/ttyS0 works and blocks
> on /dev/ttyS1?
stty -aF /dev/ttyS0
stty -aF /dev/ttyS1
I bet ttyS0 has clocal set, whereas ttyS1 doesn't.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-10-14 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 11:39 open("/dev/ttyS1", O_LARGEFILE) blocks Bernd Petrovitsch
2002-10-14 11:52 ` Russell King [this message]
2002-10-14 12:29 ` Bernd Petrovitsch
2002-10-14 13:37 ` Russell King
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=20021014125206.A2902@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=bernd@gams.at \
--cc=linux-kernel@vger.kernel.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 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.