On Fri, 11.04.14 02:23, Lennart Poettering ([email protected]) wrote: > > On Wed, 09.04.14 19:39, Richard Weinberger ([email protected]) wrote: > > > I'm also fine with ignoring OOMScoreAdjust if it fails. > > All I want is a painless Linux userspace on top of systemd within > > my Containers. :-) > > It appears to me as if this should just result in a debug message that > the oom score couldn't be changed, and we should then proceed. After all > this isn't really security sensitive property, this is just and attempt > to make a fucked up situation (which OOM is) slightly less fucked up.
What is the precise error that is returned by the kernel inside such a container? EPERM? If so, I'd recommend logging at DEBUG level if EPERM, and at WARN if any other error, but still proceed in any case. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
