delorie.com/archives/browse.cgi | search |
X-Spam-Check-By: | sourceware.org |
Message-ID: | <83c75fec0609060818x22dad9cdqe8df0de4cedf9046@mail.gmail.com> |
Date: | Wed, 6 Sep 2006 11:18:40 -0400 |
From: | "burning shadow" <burning DOT shadow AT gmail DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: bash processes <defunct> after ssh session disconnection |
In-Reply-To: | <83c75fec0608300640k356722br66b50678c5955d64@mail.gmail.com> |
MIME-Version: | 1.0 |
References: | <83c75fec0608300640k356722br66b50678c5955d64 AT mail DOT gmail DOT com> |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
I figured out this happens only if something was run from bash. For example, irssi. If disconnection occured when there was only bash active, it does not become <defunct> but stays forever with flag 'I' in processes. On 8/30/06, burning shadow <burning DOT shadow AT gmail DOT com> wrote: > Since cygwin1.dll version 1.5.20 I get bash processes became <defunct> > sometimes after SSH session disconnects. For example, today there was > a network problem and my SSH session got broken, after I reconnected, > there was 1 <defunct> process. Sometimes this does not happen. All > components I am using are updated to latest release available. > > This is something to show what is happening: > > shadow AT loshadka:~$ ps -a > PID PPID PGID WINPID TTY UID STIME COMMAND > 1588 1 1588 1588 ? 18 Aug 29 /usr/bin/cygrunsrv > 1640 1588 1640 1488 ? 18 Aug 29 /usr/sbin/sshd > 1532 1640 1532 1228 ? 18 12:37:45 <defunct> > 1576 1640 1576 1676 ? 18 12:22:09 <defunct> > I 1136 1 1136 1748 3 1000 14:11:20 /usr/bin/bash > 1496 1516 1496 1568 4 1000 16:58:58 /usr/bin/bash > 1088 1496 1088 1644 4 1000 17:08:08 /usr/bin/ps > shadow AT loshadka:~$ kill -9 1136 > -bash: kill: (1136) - No such process > shadow AT loshadka:~$ /bin/kill.exe -f 1136 > kill: couldn't open pid 1748 > shadow AT loshadka:~$ /bin/kill.exe -f 1748 > kill: couldn't open pid 1748 > shadow AT loshadka:~$ kill -9 1532 > -bash: kill: (1532) - No such process > shadow AT loshadka:~$ /bin/kill.exe -f 1532 > kill: couldn't open pid 1228 > shadow AT loshadka:~$ /bin/kill.exe -f 1228 > kill: couldn't open pid 1228 > shadow AT loshadka:~$ ps -W |grep -e bash -e defunct > 1532 1640 1532 1228 ? 18 12:37:45 <defunct> > 1576 1640 1576 1676 ? 18 12:22:09 <defunct> > I 1136 1 1136 1748 3 1000 14:11:20 /usr/bin/bash > 1496 1516 1496 1568 4 1000 16:58:58 /usr/bin/bash > shadow AT loshadka:~$ pslist |grep bash > bash 1620 8 4 111 2208 0:00:00.350 5:48:55.546 > bash 588 8 4 111 2208 0:00:00.120 5:04:13.920 > bash 1568 8 4 123 2236 0:00:00.310 0:23:27.237 > bash 1524 8 2 72 1532 0:00:00.040 0:00:00.070 > bash 1664 8 2 55 1456 0:00:00.030 0:00:00.040 > > Note: pslist is an external utility from sysinternals. > > shadow AT loshadka:~$ type pslist > pslist is /d/tools/bin/pslist > > I also want to mention that before 1.5.20 bash processes just remained > in memory and I had to kill them manually. It would be much better if > they'd got killed upon SSH disconnection, like it happens in normal > unix environment. > > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |