[Migrated content. Thread originally posted on 02 September 2003]
hello there.In an acurcl/thinclient architecture (no matter which server OS), sometimes we encounter a "zombie child runtime" problem: a server runtime has been left "on" after some abnormal thinclient termination (i.e. due to network error or improper client PC shutdown).
The zombie runtime remains active and freezed in saecula saeculorum, keeping all its resources open, including file locks, and dramatically slowing down the server machine.
The only way to solve the problem is a manual kill of the zombie. More easy, you can stop and restart the acurcl service...however, in a 20 (and more) client PC environment this is a very uncomfortable solution!
I'm looking for some automatic zombie detection and kill method, to be used on both Win and Linux/Unix server machines... runtime 5.2.1.
Any suggestion is greatly appreciated, thanks in advance to everyone!