home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.windows.x.apps:1876 comp.windows.x:21546
- Newsgroups: comp.windows.x.apps,comp.windows.x
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!ames!saimiri.primate.wisc.edu!eng.ufl.edu!alpha.ee.ufl.edu!ruck
- From: ruck@alpha.ee.ufl.edu (John R Ruckstuhl Jr)
- Subject: xmeter leaves orphans
- Message-ID: <1993Jan25.214530.431@eng.ufl.edu>
- Sender: news@eng.ufl.edu (Usenet Diskhog System)
- Organization: EE Dept at UF
- Date: Mon, 25 Jan 93 21:45:30 GMT
- Lines: 28
-
- When I fire up an "xmeter" with multiple meters, on a remote host via
- "xrsh", like (chopped from my menu):
-
- S=cpu; \
- exec xrsh gamma xmeter -cols 2 -sn -scpu 102 -update 10 -w 100 \
- -$S alpha -$S beta -$S gamma -$S delta -$S epsilon -$S zeta -$S eta \
- -$S theta -$S iota -$S kappa -$S lambda -$S mu -$S omicron -$S pi
-
- then when I kill the xmeter window, the children xmeter processes for
- the individual metered hosts live on.
- This eventually becomes a problem, as gamma gets too many processes.
-
- Has anyone else noticed this (and found a fix or workaround), or
- am I doing something wrong?
-
- It looks like I'm going to have to figure out a clever way to go to
- gamma and kill processes whose PPID doesn't refer to a current process.
- Hmmm. It looks like after the original xmeter is killed, the PPID
- becomes 1, i.e. the "init" process.
-
- What's the best way to handle this?
-
- Thanks for your comments,
- ruck
- --
- John R. Ruckstuhl, Jr. ruck@alpha.ee.ufl.edu
- Dept of Electrical Engineering ruck@cis.ufl.edu, uflorida!ruck
- University of Florida ruck%sphere@cis.ufl.edu, sphere!ruck
-