[EMAIL PROTECTED] wrote: > Having a means to avoid that your critical process gets killed > accidentally because some uncritical one decided to suck up all > system resources is, IMO, a very legitimate use case. On 2.6, where > there is no CONFIG_OOM_KILLER, you can play with /proc/<pid>/oom_adj > and make your process "unattractive" to the OOM killer (set to -17). > On older kernels you also had to include any parent processes in this > protection. I think this was fixed meanwhile. > > But I wonder why there should be no effect of CONFIG_OOM_KILLER on > 2.4. > Forgot to replay the updated kernel binaries?
Well double checked: no. At least if my .config in the linux kernel directory is not magically updated after compiling the kernel. BTW: I could not find that option in the make menuconfig configuration. Maybe it is hidden somewhere in a submenu, but at least in the .config file it is definetly disabled. Best regards, Daniel Schnell. _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
