mcdonald@AEDC-VAX.AF.MIL (Kenneth McDonald C60244 x3413) (01/09/91)
We have recently discovered that when a person logs out from our Iris running 3.3.1 at random times a process will still show up when we xeq % ps -ef This process will look something like: b30607 12294 1 0 JAN 3 ttyd3 0:01 -csh Could anyone tell me why this process stays behind? Or is there a way of making it die once you exit? (besides kill -9 or killall) NOTE: Notice that I said it occurs randomly. Mail replies directly to me at: @aedc-vax.af.mil:c60244@ccfiris.aedc Thanks.
c60244@ccfiris.aedc (Kenny McDonald) (01/09/91)
We have recently discovered that when a person logs out from our Iris running 3.3.1 at random times a process will still show up when we xeq % ps -ef This process will look something like: b30607 12294 1 0 JAN 3 ttyd3 0:01 -csh Could anyone tell me why this process stays behind? Or is there a way of making it die once you exit? (besides kill -9 or killall) NOTE: Notice that I said it occurs randomly. Mail replies directly to me at: @aedc-vax.af.mil:c60244@ccfiris.aedc Thanks. vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv | Kenneth M. McDonald * Arnold Engineering Development Center | | MS 100 * Arnold AFS, TN 37389-9998 * (615) 454-3413 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ OO AA OO O O A A O O O O AAAA O O O O A A O O OO A A OO _______________ / vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvRETURN ADDRESS:vvvvvvvvvvvvvvvvvvvvvvvvvvvv | @aedc-vax.af.mil:c60244@ccfiris.aedc | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
doelz@urz.unibas.ch (01/09/91)
In article <9101081201.aa05760@VGR.BRL.MIL>, mcdonald@AEDC-VAX.AF.MIL (Kenneth McDonald C60244 x3413) writes: > We have recently discovered that when a person logs out from our Iris running > 3.3.1 at random times a process will still show up when we xeq % ps -ef I found this one occuring the first time on 3.0B on a 4D/70. It is still in 3.3.1, and is presumably a problem at the following cases(amongst others): 1) Kill NeWS and let windows stay alive with some process running in it. 2) do a SETHOST from a VAX, and then a telnet back to it, and kill the starting process on the VAX. 3) Use a serial line input from another computer (or, in our case, a LAT terminal server) and kill the starting process on your PC or LAT. It is still not reproducable, and I usually kill it with KILL as well. Regards Reinhard