Very Computer

by **nonam** » Sun, 03 Nov 2002 02:41:34

Hi All,

When you run select() on stdin and when the end of file for stdin is
reached (either by typing Ctrl+D at the console or when EOF of a file
redirected as stdin is reached), select signals that stdin is ready for
reading. Doing a read() then returns 0. If you run select() again on
stdin, it still signals that stdin is ready for reading. Why is that so?

Thanks,
Magesh

by **Joe Halpi** » Sun, 03 Nov 2002 02:55:37

> When you run select() on stdin and when the end of file for stdin is
> reached (either by typing Ctrl+D at the console or when EOF of a
> file redirected as stdin is reached), select signals that stdin is
> ready for reading. Doing a read() then returns 0. If you run
> select() again on stdin, it still signals that stdin is ready for
> reading. Why is that so?

It's not signalling that it's ready for reading. It's signalling that
if you do a read() on the descriptor, the call will not block. The
descriptor could be some random number, which has never been
associated with any I/O device, and select() would say the same thing,
because if you tried to do a read() on it, it won't block.

See, for example

http://www.opengroup.org/onlinepubs/007904975/functions/select.html

"A descriptor shall be considered ready for reading when a call to
an input function with O_NONBLOCK clear would not block, whether or
not the function would transfer data successfully. (The function
might return data, an end-of-file indication, or an error other
than one indicating that it is blocked, and in each of these cases
the descriptor shall be considered ready for reading.)

A descriptor shall be considered ready for writing when a call to
an output function with O_NONBLOCK clear would not block, whether
or not the function would transfer data successfully."

Joe

by **Joe Halpi** » Sun, 03 Nov 2002 02:57:37

> > When you run select() on stdin and when the end of file for stdin is
> > reached (either by typing Ctrl+D at the console or when EOF of a
> > file redirected as stdin is reached), select signals that stdin is
> > ready for reading. Doing a read() then returns 0. If you run
> > select() again on stdin, it still signals that stdin is ready for
> > reading. Why is that so?

> It's not signalling that it's ready for reading. It's signalling that

Sorry, I should have said that it's not signalling that data is
available.

Joe

by **Barry Margoli** » Sun, 03 Nov 2002 03:01:42

>When you run select() on stdin and when the end of file for stdin is
>reached (either by typing Ctrl+D at the console or when EOF of a file
>redirected as stdin is reached), select signals that stdin is ready for
>reading. Doing a read() then returns 0. If you run select() again on
>stdin, it still signals that stdin is ready for reading. Why is that so?

Select is telling you that read() won't block. It didn't, did it?

--

Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.

by **Dan Merc** » Sun, 03 Nov 2002 03:04:07

> Hi All,

> When you run select() on stdin and when the end of file for stdin is
> reached (either by typing Ctrl+D at the console or when EOF of a file
> redirected as stdin is reached), select signals that stdin is ready for
> reading. Doing a read() then returns 0. If you run select() again on
> stdin, it still signals that stdin is ready for reading. Why is that so?

> Thanks,
> Magesh

Because stdin points to a device that is always ready, like a filesystem
file. It will only block for a pipe, fifo, socket or tty. Even
for those it may unblock with no chars (for instance, by
sending EOF by hitting Control D).

--
Dan Mercer

If responding by email, include the phrase 'from usenet'
in the subject line to avoid spam filtering.

Opinions expressed herein are my own and may not represent those of my employer.

by **Michael Kerris** » Sun, 03 Nov 2002 18:53:25

>> When you run select() on stdin and when the end of file for stdin is
>> reached (either by typing Ctrl+D at the console or when EOF of a
>> file redirected as stdin is reached), select signals that stdin is
>> ready for reading. Doing a read() then returns 0. If you run
>> select() again on stdin, it still signals that stdin is ready for
>> reading. Why is that so?

>It's not signalling that it's ready for reading. It's signalling that
>if you do a read() on the descriptor, the call will not block. The
>descriptor could be some random number, which has never been
>associated with any I/O device, and select() would say the same thing,
>because if you tried to do a read() on it, it won't block.

Small correction here - it looks as though you are saying that select() on a
closed file descrptor will return "ready" - not so, it will return the error
EBADF.

Cheers

Michael

Very Computer

select on stdin at EOF

select on stdin at EOF

select on stdin at EOF

select on stdin at EOF

select on stdin at EOF

select on stdin at EOF

select on stdin at EOF