On Mon, Mar 26, 2001 at 01:33:05PM +0200, Ingo Oeser wrote:
> > The point being, my database shouldn't be selected for
> > termination. Nobody ever got fired for kill -9'ing netscape,
> > but Oracle is a different story. I urge you, consider the
> > patch.
>
> No, you got fired for not setting ulimits. Your boss is right
> then!
>
> ulimit -d 65536
> ulimit -v 81920
Ehm, right.
Running netscape (or any other memory hog which doesn't belong on a server)
on a production server seems reason enough for a little talk with your boss.
On the other hand, if no other apps are running on your box, and Oracle gets
killed due to OOM, you probably have underestimated your hardware needs, or
Oracle has gone haywire, which is a good reason for killing it.
Thus, nothing seems wrong with the current kill algorithm to me...
Just my two cents,
--
Q_. Jasper Spaans <[EMAIL PROTECTED]>
`~\ http://jsp.ds9a.nl/
Mr /\ Tel/Fax: +31-20-8749842
Zap Move all .sig for great justice!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
