> Actually what you're telling us is that there's a defect in (presumably Linux) > which should be documented in read(2). Once you've gotten it documented in >the proper place (Linux manpages), then others can use the documentation.
It is normal for read() to return 0, without an error when EOF is reached. This is how you detect EOF/closed on sockets and files. Should TTY behave differently? Stian Skjelstad > > > >
