home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.amiga
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!usc!sol.ctr.columbia.edu!news.columbia.edu!cunixa.cc.columbia.edu!wyk1
- From: wyk1@cunixa.cc.columbia.edu (Won Y Kim)
- Subject: Re: 2.1 Kernel bug workaround..??
- Message-ID: <1992Aug18.032344.13269@news.columbia.edu>
- Sender: usenet@news.columbia.edu (The Network News)
- Nntp-Posting-Host: cunixa.cc.columbia.edu
- Reply-To: wyk1@cunixa.cc.columbia.edu (Won Y Kim)
- Organization: Columbia University
- References: <Bt3y6p.7Bn@cs.columbia.edu> <1992Aug17.213613.28703@nntpd.lkg.dec.com> <1992Aug18.011807.27495@isc-br.isc-br.com>
- Date: Tue, 18 Aug 1992 03:23:44 GMT
- Lines: 25
-
- In article <1992Aug18.011807.27495@isc-br.isc-br.com> ricks@odin.isc-br.com (Rick Schaeffer 99) writes:
- >In article <1992Aug17.213613.28703@nntpd.lkg.dec.com> barrett@pamsrc.enet.dec.com writes:
- >>
- >>
- >>You could do what I do. Add a crontab entry that reboots your system
- >>every night at 3am. Since I added that, I see a panic perhaps once
- >>a month now rather than once a week.
- >>
- >
- >You might just keep an eye on the X server (use "ps -el | fgrep X") and
- >kill it when it get's too big. In my experience, it's the main (or "only")
- >culprit and it's much quicker to just kill it. NOTE: if you are running
- >with xdm, just logging off isn't enough...you have to go to the console
- >as root and actually "kill" the server (whose pid shows up in the ps
- >output from the example above). xdm will automatically respawn it.
- >I suppose that someone could come up with a script that did this
- >automatically...personally I just keep an eye on it (it doesn't grow
- >all *that* fast :-) ) and kill it when it's size gets up over 6 meg
- >or so.
-
- Thanks.. I will try this too!
- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
- Won Kim. Programmer ReProgrammer.
- "I am the SuperGrunt. The *Orginal* SuperGrunt. Perhaps you have heard of me?"
- - The Orginal SuperGrunt
-