🚀 go-pugleaf

I thought I'd do a little investigating so I could say exactly what's going
on.

In article <1990Nov7.050320.11615@opusc.csd.scarolina.edu> I write:
+
+  [stuff that doesn't need repeating]
+
+						..........The problem occurs
+when I use VLT while getty is running.  getty gets out of the way as it is
+supposed to, and my outgoing calls work fine, but after certain actions (eg,
+if I hang up the modem with VLT -- this is the only one I can currently
+reproduce, though I think there may be others), getty will seemingly
+disappear.  status reports it is gone, and so does Xoper.  Often, if I
+attempt to restart getty after this has happened, the machine will crash, and
+when it does guru, it's a 00000004.xxxx - type guru (which one is this? 

Here's an example.  getty is run in the background, with the command

  run >nil: <nil: getty -Smodem0.device -U0 -B2400 -B1200 -Mh -m0 -r2

I fire up VLTjr 4.846, and call up anyone.  As long as I am connected,
everything is fine.  If, however, I use the hangup command (out of the menu,
or right-A-H), then there is a bit of disk activity, and getty is gone.  If I
quit VLT, and then try to either restart VLT or restart getty, we get a
software falure.  The last two times I tried it, I got a 00000004.xxx when I
tried to restart VLT, and then when I repeated the experiment, and try
restarting getty, I got a 00000003.xxx (yeah!  Ain't never gotten one of
those, before!).

Any ideas?

ken
-- 
     Ken Yarnall                 ///   yarnall@usceast.cs.scarolina.EDU
      Math Department, USC   \\\///   yarnall@ucseast.UUCP
       Columbia, S.C. 29208   \\\/   (803)777-5218
    `You'd better tie me up.' -- from the movie, "Tie Me Up, Tie Me Down"