"Vadim Goncharov" <vadim_nuclight@mail.ru> writes:Well, technically, it was because the server didn't have enough RAM for the workload it was given. Turning off memory overcommit wouldn't fix that, it would just change the symptoms. I don't know of a single server OS that doesn't overcommit memory. The only difference between them is how they behave once the shit hits the fan. Anyway, as somebody else mentioned, the details are in the archives - if you don't know enough English to find them there, I don't see how having them summarized in English will help. If the language barrier really is a problem, ask someone who speaks your language to help you. DES -- Dag-Erling Smørgrav - des@des.no _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Linus Torvalds | Re: Long delay in resume from RAM (Was Re: [patch 00/69] -stablereview) |
| Parag Warudkar | BUG: soft lockup - CPU#1 stuck for 15s! [swapper:0] |
git: | |
| Andi Kleen | [PATCH RFC] [4/9] modpost: Fix format string warnings |
| Rick Jones | Re: Network latency regressions from 2.6.22 to 2.6.29 |
| Antonio Almeida | HTB accuracy for high speed |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
