Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!houxm!houxz!vax135!cornell!uw-beaver!tektronix!hplabs!sri-unix!lcc.bob@UCLA-LOCUS.ARPA
From: lcc.bob@UCLA-LOCUS.ARPA
Newsgroups: net.unix-wizards
Subject: Clarification of device driver subtleties
Message-ID: <382@sri-arpa.UUCP>
Date: Tue, 24-Jul-84 18:09:57 EDT
Article-I.D.: sri-arpa.382
Posted: Tue Jul 24 18:09:57 1984
Date-Received: Fri, 27-Jul-84 08:21:38 EDT
Lines: 13

From:            Bob English <lcc.bob@UCLA-LOCUS.ARPA>

No, sleep doesn't do anything strange when called at an elevated priority.

Yes, signals can interrupt the sleep if the sleep priority is > PZERO.

If an interrupt occurs the process will do a longjmp to whereever its
longjmp structure points.  Unless you have made special
arrangements, this will probably pop you back into user mode with
an interrupted system call.  If the process has some kernel resource 
locked, the resource will remain locked indefinitely.

--bob--