does anyone knows how the ulimit bash (or whatever shell you like) command works? i’m currently running a few instances of the same program on a big server, and it happened yesterday twice that the programs together ate up all available memory (some of the instances using much more than others). there was a hard ulimit set on memory, and the result was that all these processed were killed. not just the one violating the memory limit in that moment.
this sucks pretty much, since this destroyed some cpu days of work. does anyone knows why ulimit is doing this? i assume that the rationale is to stop fork bombs, but in this case this is really, really annoying. killing one of the processes would have been perfectly enough…
so, if anyone has good documentation on how ulimit works, whether it is possible to change this behaviour, and whether this is actually intended or a bug, i would like to hear about it…
felix.
settings.
other languages.
pages.
friends.
things i like to read.
categories.
recent posts.
archives.
places.
europe finland lapland ivalo france germany baden-württemberg lower saxony oldenburg north rhine-westphalia lüdinghausen saxony sächsische schweiz norway scandinavia lappland switzerland alps basel pratteln z-7 central switzerland glarus graubünden engadine ticino zürich zürcher oberland hinwil zürich üetliberg north america canada alberta calgary rocky mountains jasper newfoundland yukon oceans
comments.