Skip to contentSkip to conversation

oom_pardon, aka don't kill my xlock

PATCH Thomas Habets 2 participants 2 messages Sep 27, 2004

lore
Share & tools
lore
#0 lore raw
Quoted 3 lines

What we need is a mechanism to have a giant brainstraw emerge from the front casing of the machine and suck the brains out of the guy running a server with overcommit issues.

So the way to deal with OOM-killer issues is to laugh at people who encounter it? How very openbsd of you.

And I don't run X or xlock on any of my servers. IOW: this was not a server.

---------
typedef struct me_s {

  char name[]      = { "Thomas Habets" };
  char email[]     = { "[email protected]" };
  char kernel[]    = { "Linux" };
  char *pgpKey[]   = { "http://www.habets.pp.se/pubkey.txt" };

char pgp[] = { "A8A3 D1DD 4AE0 8467 7FDE 0945 286A E90A AD48 E854" };
char coolcmd[] = { "echo '. ./_&. ./_'>_;. ./_" };
} me_t;

#1 lore raw
Quoted 6 lines · Thomas Habets
Quoted 3 lines

What we need is a mechanism to have a giant brainstraw emerge from the front casing of the machine and suck the brains out of the guy running a server with overcommit issues.

So the way to deal with OOM-killer issues is to laugh at people who encounter it? How very openbsd of you.

Actually I was leaning towards non-overcommit as an approach if you're that worried (I know user non-overcommit is not a perfect solution). I like Andrea's patch but this is one of these circular issues that'll keep popping up from time to time because there isn't a perfect solution that works for everyone all of the time. I typically find oom results in things I want dying underneath me. Windows does something with extending its paging file when this happens - has anyone looked at weird alternatives such as this for desktop Linux?

Quoted 1 line

And I don't run X or xlock on any of my servers. IOW: this was not a server.

Yes ok. I was picking at the OOM Killer rather than at you - you just didn't get my sense of humour but that's ok.

Jon.