Re: 4GL "Prompt" and zombies

In <674.365.uupcb@digitec.co.za> billy.wheeler@digitec.co.za (Billy Wheeler) writes: >JL> We have a 4GL (4GL version 4.11 and 5.01.UD4 on HP9000's) application that >> is being accessed over telnet from a PC over the network. Occasionally >> (we think the #*@# users are rebooting the PC), the 4GL program >> becomes a zombie (top shows a ? as it's owning terminal) and the 4GL program >> sucks up 95-100% of the CPU time. All the code is doing is waiting for the >> user to enter data via a prompt command. >JL> Does anyone have any experience with this? Seen this on a DG and a Dell too. (On the Dell, heh heh, a simple 'kill 999' would send the whole machine into oblivion, as if it somehow adjusted the nice value to -20 (bear in mind that nice values < 0 mean signals are now ineffective and give it a greater share of cpu time).) I've found that a kill -SEGV on the fglgo runner does the trick nicely, and seems to get the sql process to go away cleanly as well. -- Andrew Burt aburt@du.edu "But if he was dying he wouldn't bother to carve "Aaaaargh", he'd just say it."