Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!news.msfc.nasa.gov!elroy.jpl.nasa.gov!swrinde!ringer.cs.utsa.edu!news.cais.net!zippy.cais.net!news.vni.net!cnordin From: cnordin@hq.vni.net (Craig Nordin) Newsgroups: comp.unix.bsd.bsdi.misc Subject: Zombies? We don't need no stenkin' Zombies! Date: 18 Oct 1995 02:27:47 -0400 Organization: Virtual Networks Lines: 22 Message-ID: <cnordin.813997458@news.vni.net> NNTP-Posting-Host: hq.vni.net X-Newsreader: NN version 6.5.0 #6 (NOV) Why don't apps die like they are supposed to when a connection is closed? tin, nn, vi, irc, all of 'em are likely to stick around when their user cuts the connection -- at least one out of three times. And not only do they stick around, but they stick around running up all available cpu resources. What the heck is this and how do I get rid of it? Sure, I can start a campaign for all users to log-out properly, but that doesn't account for net-failure or a modem-drop. These processes should die with a little bit of style! Thanks! -- -- "He who loses control, loses." Andre Brauer, Homicide