When Kill dosen't work 4342

Tony Lawrence

Well, I do not know about that, because if the interrupt was somethink like one from a SCSI controller, it could be from any of the 15 devices on it, and I do not necessarily know to which process that interrupt belongs. It is not necessarily a simple thing to monkey around in here. Depending on how the interrupt handling and device drivers are done in Linux, perhaps it is simple, but I am way out of my depth here. (I once wrote an OS where this was, in fact, simple, and unwanted interrupts were all silently discarded, but I have no reason to believe Linux works this way.) (one of) the database administrator(s), or the web server administrator, the e-mail administrator, etc., so I would have to coordinate with all of them (or at least one of them). And it might be that an advanced user might have a suite of cooperating sequential processes that was in trouble, and I would not necessarily even know about him or her.

-- .~. Jean-David Beyer Registered Linux User 85642. V PGP-Key: 9A2FC99A Registered Machine 241939. ^^-^^ 08:45:00 up 49 days, 2:38, 3 users, load average: 4.35, 4.19, 4.12