[Thinlinc-technical] tlwebadm/tlwebaccess (tlstunnel) producing zombies
Tobias Oetiker
tobi at oetiker.ch
Fri Jul 19 19:44:50 CEST 2013
Today Jens Langner wrote:
> Hello,
>
> I dunno if this is a known issue, but having ThinLinc running for
> a while now I often see that the number of Zombie processes
> increases on the server. Search for the reason of the zombies I
> see the following:
>
> -- cut here --
> root at saturn:~# ps aux | grep tlstunnel
> root 6371 0.0 0.0 11816 928 pts/28 S+ 19:37 0:00 grep --color=auto tlstunnel
> root 61846 0.0 0.0 11864 1380 ? S Jul14 0:00 tlstunnel --port 1010 --maxbuf 16384 --un_sock /var/run/tlwebadm.sock --cert /opt/thinlinc/etc/tlwebadm/server.crt --certkey /opt/thinlinc/etc/tlwebadm/server.key --logname tlwebadm
> root 64262 0.0 0.0 0 0 ? Z Jul15 0:00 [tlstunnel] <defunct>
> root 64263 0.0 0.0 0 0 ? Z Jul15 0:00 [tlstunnel] <defunct>
> root 64264 0.0 0.0 0 0 ? Z Jul15 0:00 [tlstunnel] <defunct>
> root 64265 0.0 0.0 0 0 ? Z Jul15 0:00 [tlstunnel] <defunct>
> root 64266 0.0 0.0 0 0 ? Z Jul15 0:00 [tlstunnel] <defunct>
> root 64267 0.0 0.0 0 0 ? Z Jul15 0:00 [tlstunnel] <defunct>
> -- cut here --
>
> As you can see tlstunnel of tlwebadm is somehow producing zombies
> at some point. The same actually happens with the tlwebaccess of
> ThinLinc. Is this behavior known and if so, is there some kind of
> fix/workaround for it? The good thing is, however, that as soon
> as I restart tlwebaccess and tlwebadm the zombie processes are
> gone.
in other words, tlwebaccess isnot waiting for its children ...
that should be an easy fix for people wo work with the
non-obfuscated source ...
cheers
tobi
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi at oetiker.ch ++41 62 775 9902 / sb: -9900
More information about the Thinlinc-technical
mailing list