Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!mailrus!purdue!haven!mimsy!chris
From: chris@mimsy.umd.edu (Chris Torek)
Newsgroups: comp.unix.questions
Subject: Re: uucico hanging. LBOLT???
Keywords: Sun 2/170, SunOS 4.0 w/yapt 5.5
Message-ID: <25998@mimsy.umd.edu>
Date: 12 Aug 90 23:05:39 GMT
References: <5442@quack.UUCP>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 28

In article <5442@quack.UUCP> mrapple@quack.UUCP (Nick Sayer) writes:
>The process becomes a zombie with the notation "LBOLT" listed as the
>event the process is waiting for (as reported both by ps -axlw and
>sps -va). What is an lbolt and how do I "give it one"

`lbolt' is the `lightning bolt' interrupt (shazam! :-) ), which occurs
once per second (in V6 it may have been once every 4 seconds or 4 times
a second; all I remember is that someone once mentioned that it changed
between V6 and V7).

Since the lightning bolt wakeup happens continually, it obviously is
waiting for something else, and merely using lbolt as a convenient way
to check periodically.  (This is what lbolt is for.)

>or kill the unkillable process?

To dream... the impossible dream....  Oh, right.  Well:

>Note that bringing the carrier up on the modem does not work ..

This probably means the answer is: `you can't'.

(Hmm, more verses: `To play the unbeatable rogue/To kill the
unkillable process/To hack where the guru won't go...' :-) )
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@cs.umd.edu	Path:	uunet!mimsy!chris
	(New campus phone system, active sometime soon: +1 301 405 2750)