[Gllug] Uninterruptible/killable processes

t.clarke tim at seacon.co.uk
Mon Jul 1 11:28:55 UTC 2002

Message from:-
Tim Clarke  (tim at seacon.co.uk)
Seacon Group Ltd / Seacon Terminals Ltd,
Tower Wharf, Northfleet, Kent, DA11 9BD, UK
Telephone: +44 (0)1474 320000
      Fax: +44 (0)1474 329946

Nix and Alain wrote further on the subject.

I am suitably illuminated !

As a matter of interest, a previous operating system (the innards of which I
was more familiar with, having been required to wriute a device-deriver) I used
had the ability for a privileged user to send an 'abort' request to the o-s
for a named device which would cause the kernel to re-enter the driver code at
a specified point (every driver if I recall correctly had to have such an entry-
poitn defined), terminate the i-o operation and return an error to the
requesting task/process.  This was a sort of last-chance method to kill of a
task which was stuck due to the kernel failing to return from an i-o call.


Gllug mailing list  -  Gllug at linux.co.uk

More information about the GLLUG mailing list