This is the mail archive of the
mailing list for the Cygwin project.
RE: Weird top bug?
- From: "Chris January" <chris at atomice dot net>
- To: <avadekar at certicom dot com>,"Cygwin at Cygwin dot Com" <cygwin at cygwin dot com>
- Date: Fri, 6 Jun 2003 23:44:49 +0100
- Subject: RE: Weird top bug?
> 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:
> while true;
> ping -n 1 remoteMachine >/dev/null
> sleep 60
> I typically run this as a background task (vping &), then telnet to
> 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
> processes, and the open shell still has an entry in that list?
Please post the output of cygcheck.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html