Re: fglgo eating cpu

We have Informix SE 4.0 running on a Sun SPARC. and we have had similar problems with fglgo. We have a large number of users who run application programs from their local machines, but the program essentially is running on a server remotely. When users kill the window in the middle of a query or a report, the sqlexec dies but the fglgo starts eating the cpu and remains forever unless we kill it. -fenil >In response to gaukur@rhi.hi.is whose fglgo eats cpu: >We have similar problem frequently on our Unisys 5000, runniing sql SE 2.10G >where a user is running a report script which is waitng for input from the >terminal (accepting input before running the report). If our off-brand LAN >disconnects them, or the disconnects from it without first deleting(CANCEL) our >of the prompt, the sql process becomes a child of PID #1 and takes on a life >of its own, eating memory til we run out. When we do a ps -efl and look in >the SIZE column it gets as big as our kernal tuning will allow, which is too >much for anything else to run. System halts. Kernal is tuned that way for >various nightime process which need it. I was just hoping our soon-to-be- >installed 4.0 would repair the problem! Meanwhile, we have a scripts that runs >from cron every 5 minutes and kills any process bigger than XXXX. >Does anyone else have SQL/SE that does this? Is 4.0 better?