Xref: utzoo comp.unix.internals:2122 comp.unix.wizards:24203 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!ucsd!pacbell.com!att!cbnews!rock From: rock@cbnews.att.com (Y. Rock Lee) Newsgroups: comp.unix.internals,comp.unix.wizards Subject: Re: Help with 4.3 mod to kill uninteruptable procs. Message-ID: <1991Feb21.150624.28287@cbnews.att.com> Date: 21 Feb 91 15:06:24 GMT References: <1991Feb19.001941.29928@lynx.CS.ORST.EDU> <1991Feb20.232118.11035@odin.diku.dk> Organization: AT&T Bell Laboratories Lines: 17 In article <1991Feb20.232118.11035@odin.diku.dk> thorinn@diku.dk (Lars Henrik Mathiesen) writes: >The first class you probably shouldn't mess with. If you're lucky, >removing the sleeping process will only result in the loss of some >buffer. In worse cases, you get permanently un-openable devices or >crashes. The real cure for these is to rewrite _each_case_ to sleep at >interruptible priority and clean up properly (more than a class >project, I think). [this is a guess, not an argument] The "permanently un-openable devices" can only happen in the case of open. Because open wasn't "complete" so the close call in the exit cannot do a correct clean up. Please correct me if I miss something. Y. Rock Lee, att!cblph!rock rock@cblph.ATT.COM Brought to you by Super Global Mega Corp .com