Alan Coopersmith wrote: > X won't get ENODEV until select() returns that there's something to read > on the device and we attempt to read() from it. If neither the kernel > nor HAL somehow signal X, we'll never notice.
If you're selecting on the device, and the device itself is removed, will you wake up with that fd in the errorfds list? If not, I think that's a kernel bug, and you certainly should. If you do wake up but don't recognize that errorfds is as interesting as read()==-1, then that sounds like an application problem. -- James Carlson 42.703N 71.076W <carlsonj at workingcode.com>
