Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Fri, 6 Jun 2003 23:50:01 +0100
From: Elfyn McBratney <elfyn AT is DOT ubertales DOT co DOT uk>
X-X-Sender: elfyn AT ellixia
Reply-To: cygwin AT cygwin DOT com
To: avadekar AT certicom DOT com
cc: cygwin AT cygwin DOT com
Subject: RE: Weird top bug?
In-Reply-To: <ICEBIHGCEJIPLNMBNCMKOEEGCHAA.chris@atomice.net>
Message-ID: <Pine.CYG.4.55.0306062348420.1400@ellixia>
References: <ICEBIHGCEJIPLNMBNCMKOEEGCHAA DOT chris AT atomice DOT net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 6 Jun 2003, Chris January wrote:

> > I've stumbled across some peculiar behaviour for top.  I've got
> > the following
> > script (vping) that I use to keep a VPN connection alive:
> > 	#!/bin/sh
> > 		while true;
> > 		do
> > 			ping -n 1 remoteMachine >/dev/null
> > 			sleep 60
> > 		done
> >
> > I typically run this as a background task (vping &), then telnet to
> > remoteMachine.
> >
> > Now when I quit telnet, then exit the shell (vping was run from),
> > the shell
> > stays around.  My script has a stdout handle, I suppose.  That's OK, I can
> > close the window with the mouse, and then vping dies.  Seems
> > normal.  But if I
> > leave the shell open after typing exit, then run top in another shell, it
> > clears the screen, shows exactly one line of output (in this
> > specific case):
> > 	 15:23:03 up  8:00,  2 users,  load average: 0.00, 0.00, 0.00
> >
> > and locks up.  Control C does not regain shell control.
> >
> > If I open another shell and use ps to find the process number for
> > top, I can
> > kill it (kill pid, no explicit signal type).
> >
> > It doesn't seem to me that my specific script should have
> > anything to do with
> > how top is behaving, but I supose it is possible.  Seems more like top is
> > having trouble because the parent process of my script is no longer valid.
> > Maybe the parent process is gone, but top uses a windows thing to
> > enumerate
> > processes, and the open shell still has an entry in that list?
> Please post the output of cygcheck.

As per <http://cygwin.com/problems.html>. :-)

Elfyn

-- 
Elfyn McBratney (mailto:spambot AT is DOT ubertales DOT co DOT uk)
Systems Administrator
ABCtales.com / Ubertales.co.uk


--
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/