Ar Maw, 2006-10-03 am 17:07 -0700, ysgrifennodd Manish Neema:
> Thanks Keith for the response.
>
> My explanation earlier is not clear. The "automount" process dying with
> restrictive overcommit settings is not because of the OOM kill. It looks
> like some bug with "automount" binary itself causing it to exit when it
> could not service a new request.
>
> "cd /remote/something" when the system is out of (allocate'able) memory
> causes the below events (obtained from /var/log/messages)
>
> Oct 3 13:35:32 gentoo036 automount[2060]: handle_packet_missing: fork:
> Cannot allocate memory
> Oct 3 13:35:34 gentoo036 automount[2060]: can't unmount /remote
Your kernel is behaving correctly if it does this in mode 2. You need
more memory or to better set resource limits on what is running.
Alan
-
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]
