![]() | |||||||||||||
Messages in this thread |
> >Having a program be stuck in read/write ignoring signals, so that > >Control-C, Control-Z and kill don't work on it, while it's waiting for > >some network operation, is a horrible thing. > > I've made it a personal crusade to eliminate D state. In addition to all > the damage done by computer resources being locked up, something about my > computer ignoring me rankles me on a personal level. Very true. FUSE currently handles it by allowing SIGKILL, but no other signals. Interrupting file operations would be very nice, but unfortunately apps just don't handle it very well (even in case SuS actually allows EINTR). > I believe this proposal is about making open() hang, which I think is even > more painful than having read/write hang. open() is often designed to > block much more casually. Then why the hack do people write programs that get some alarm signal 100 times a second _while_ doing the open. If they do that then trying to make it interruptible is sort of useless. Miklos - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-05-21 08:25 [from the cache] ©2003-2008 | |||||||||||||