Date: Thu, 17 Jul 2008 14:43:40 GMT From: Mark McDonagh <payload@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/125719: shells/pdksh, zombie process's occouring on SMP Machines from scripts Message-ID: <200807171443.m6HEhe3A004071@www.freebsd.org> Resent-Message-ID: <200807171450.m6HEo1jO007302@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 125719 >Category: ports >Synopsis: shells/pdksh, zombie process's occouring on SMP Machines from scripts >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jul 17 14:50:00 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Mark McDonagh >Release: 7.0-RELEASE >Organization: >Environment: FreeBSD freebsd.com 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: When using the pdksh shell the following script on a SMP system hangs after running for about 5 minutes. ############# # # debug.sh # while true; do echo `cat /var/run/sshd.pid` done ############# After running for 5 to 10 minute debug.sh stops outputting the contents of /var/run/sshd.pid and the script appears to be in sigsuspend mode. When you examine the process table there appears to be defunct child process whose parent is debug.sh. The problem doesn't occur on single CPU systems, however on multiple cpu systems the problem happens within minutes of starting the debug.sh script. >How-To-Repeat: 1) make pdksh your default shell 2) start the following script ############# # # debug.sh # while true; do echo `cat /var/run/sshd.pid` done ############# >Fix: None Known >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200807171443.m6HEhe3A004071>