From: "Carlos Fernández Sanz" <cfs-lk@fulanito.nisupu.com>
To: <linux-kernel@vger.kernel.org>
Subject: Fw: select(), EOF...
Date: Mon, 20 Aug 2001 22:38:41 +0200 [thread overview]
Message-ID: <006d01c129b8$1957f2c0$0414a8c0@10> (raw)
(sorry if this is a dupe, I haven't seen it come from the list, so I'm
resending as plain ASCII in case majordomo kills messages with strange
stuff)
Hi,
I need to do something similar to tail -f.
I was hoping that select() or poll() would block my process after reaching
EOF but (as the man says) EOF doesn't cause read() to block so select() and
poll() both say I can read. The result is (obviously) that my program waits
actively and uses all the CPU.
What's the right way of doing this? I assume the kernel provides facilities
to find out if there is new data to read (other than EOF).
Thanks.
next reply other threads:[~2001-08-20 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-20 20:38 Carlos Fernández Sanz [this message]
2001-08-20 20:45 ` Fw: select(), EOF Ignacio Vazquez-Abrams
2001-08-20 20:56 ` Carlos Fernández Sanz
2001-08-20 21:00 ` Ignacio Vazquez-Abrams
2001-08-20 21:09 ` Carlos Fernández Sanz
2001-08-20 21:29 ` Ignacio Vazquez-Abrams
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='006d01c129b8$1957f2c0$0414a8c0@10' \
--to=cfs-lk@fulanito.nisupu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox