3 ms·
Nobody "gives" set amounts of memory to their processes at all, so this thinking is backwards to begin with. The vulnerability is legitimate.
by lawnchair_larry 9y ago
Nobody "gives" set amounts of memory to their processes at all, so this thinking is backwards to begin with. The vulnerability is legitimate.
- yuubi 9y agoI seem to remember that the installation directions included something to limit memory size, and trying to install without reading the directions would fail well before opening a listener port.
- X-Istence 9y agosystemd by default limits programs to a certain amount of memory (this bit me in the ass while working on getting OpenStack running on Ubuntu 16.04, and MySQL would get killed because of memory usage). Various other systems also limit with things like /etc/login.conf on FreeBSD. There is also /etc/security/limits.conf on Linux for non-systemd stuff. Limits for memory usage/open files/things of that nature are natural. You don't want one runaway process to cause the rest of your system to OOM.