Xref: utzoo comp.unix.questions:6820 comp.unix.wizards:8195 comp.unix.microport:577 Path: utzoo!mnetor!uunet!husc6!bbn!mit-eddie!ll-xn!ames!umd5!vrdxhq!daitc!viusys!rwb From: rwb@viusys.UUCP (Rick) Newsgroups: comp.unix.questions,comp.unix.wizards,comp.unix.microport Subject: Re: Trouble killing processes in SysV/AT Message-ID: <270@viusys.UUCP> Date: 2 May 88 11:13:23 GMT References: <3950@killer.UUCP> <3951@killer.UUCP> <468@micropen> <625@vsi.UUCP> Reply-To: rwb@viusys.UUCP (Rick) Organization: Unisys D.A. MINIS Branch, McLean, VA Lines: 21 In article <625@vsi.UUCP> friedl@vsi.UUCP (Stephen J. Friedl) writes: >In article <468@micropen>, dave@micropen (David F. Carlson) writes: >< In article <3951@killer.UUCP>, wnp@killer.UUCP (Wolf Paul) writes: >< > Can anyone enlighten me as to what causes a process to become "immortal" >< > in System VR2, or Microport UNIX System V/AT, to be more specific? < much good info on PZERO, sleep(), etc deleted > >you can write a program that looks this address up in the /unix >namelist and gives a clue for what the process is waiting. I'm not familiar with what's distributed with Microport, but if 'crash' is included, the command "ds address", where "address" is the WCHAN, or event address, will return the name and offset from the nearest symbol to that address, hopefully the name of the sleep queue on which the process is sleeping, e.g. "physio +2". Of course, this still doesn't allow you to kill the process; as Steve points out, anything sleeping at a priority less than (greater than?) PZERO will not be awakened to process a signal. Only wakeup() will do that . . . Rick Butland