-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/31/07 12:37, Jeff Davis wrote:
> On Tue, 2007-01-30 at 20:44 -0800, David Fetter wrote:
>> On Tue, Jan 30, 2007 at 04:43:14PM -0800, Richard Troy wrote:
>>> On Tue, 30 Jan 2007, Mark Walker wrote:
>>>> I don't know. My customers expect 24/7 reliability. They expect
>>>> to be able to access their info anywhere in the world over a
[snip]
>> The OOM killer in Linux is, indeed, asinine. You can shut it off,
>> though, and systems administrators worth their salt know this and do
>> it as a matter of routine. If you have some strategy that doesn't
>> involve those hangs as a consequence, I'm sure you can get an audience
>> from the Linux kernel people and/or the FreeBSD ones.
>>
>
> I know this is off-topic for this list, but is there a place I can get
> some details about linux OOM killer, and the conditions that cause this
> OS hang when you turn off the OOM killer? I'd like to really know what's
> happening, and also know more about the OS hanging condition that you're
> talking about. I'd also like to know how safe the "safe" settings really
> are ( vm.overcommmit_memory=2 and vm.oom-kill=0? ).
No, but I *can* tell you that it's easy to create swap *files* and
enable them at a moment's notice. "man mkswap" tells you how to
make them. Supposedly, the 2.6 kernels fixed any performance
deficits to using swapfiles.
> Right now I'm using FreeBSD (in a large part due to the Linux OOM
> killer), but I have a different set of problems on FreeBSD.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFwObOS9HxQb37XmcRAmyvAJ9tpJN6EhWRoPEI62f5gF8q1URe7wCguq+X
uw3xex5Jd+IbvhElAAofH2E=
=pS5o
-----END PGP SIGNATURE-----
