On Sat, 11 Nov 2006, Christian Kujau wrote:
> I think I'm more interested as to why the OOM killer seems to kill innocent
> apps at random. I can imagine that it's not easy for the kernel to tell which
> userland-application is using up too much memory. Hm, egrep -r "OOM|ut of
> memory" Documentation/ does not reveal much :(
A look at /proc/*/oom_score might shed some light on the "at random" part.
I.e., doing
for job in /proc/[0-9]* ; do \
echo -e "`cat $job/oom_score` \t $job \t `head -c50 $job/cmdline`"; \
done | sort -n
the last process listed is considered the biggest memory hog of the
moment (Of course, this still does not tell _why_).
Tim
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
