Maybe there should be a memd that watches memory usage and deals with the
problem. The simplest solution would be for memd to notify the console of
the problem and let root deal with it. Alternatively, I suppose that memd
could just gracefully kill the offending process(es).
Lets say I do something stupid like write an infinite fork while I'm in
userland. Why cant a daemon notice that user person is being a memory hog
and kill off his biggest process?
Of course, something like a memd might be a substantial performance hit
also.
How do other unix oess handle this one?
Brett G. Person
person@slackware.com
person@netcenter.net
On Wed, 15 Dec 1999, Chris Wedgwood wrote:
> > Dunno if this is a bug or if it's supposed to happen like this, but an
> > ordinary user was able to crash inetd on my computer by doing a "make -j"
> > on a very big job.
> >
> > Is this normal or should I supply more information?
>
> It's normal an IMO a bad thing -- but not trivial to fix.
>
> My guess is the system run out of ran so the kernel killed something
> at random, which in your case was inetd.
>
> FreeBSD kills the largest process running which may not be a
> brilliant way to go, but is better than killing something at random
> IMO (flames in private, we don't need this thread again!)
>
>
>
>
> -cw
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/