I’ve never tried to adjust this, but you might find this useful:
The gist is that there are some settings which might be read or written in “
/proc/sys/”, and that the file for setting this at boot is “
/etc/sysctl.conf”, while setting this on command line as a one time test is with the “
sysctl” tool (run with
In that article you will see this:
The commands above refer to files under “
/proc/sys/”. To see the current content the command “
sysctl vm.panic_on_oom” has via cat of a file:
…or cat of kernel.panic:
In some cases sysctl as a command merely echos a new value into the file (if the file is writable). If you were to add something like “
kernel.panic=5” to “
/etc/sysctl.conf”, then upon boot this value would go into “
/proc/sys/kernel/panic” in the same way that the command “
sysctl kernel.panic=5” would do. Again, be careful about modifying the actual “
/etc/sysctl.conf” unless you are certain what you are doing is correct.
Low memory can be a serious problem, and I would be careful about disabling a warning or OOM killer. If the message is just interfering by being visible where it is inconvenient, then perhaps you could simply start your app redirecting stderr to “
/dev/null”. If it is the desktop sending pop-ups, then there is probably a desktop specific mechanism to prevent the pop-up, but I don’t know what that would be.
Btw, if it turns out to be disk space filling, then this can leave your system without a rescue ability other than to flash it again (possibly cloning first) if you can’t log in to reduce disk content clutter. My assumption with the above is RAM out of memory.