Date: Sat, 05 Mar 2016 12:29:50 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-threads@FreeBSD.org Subject: [Bug 204426] Processes terminating cannot access memory Message-ID: <bug-204426-16-umNKXZWXWM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-204426-16@https.bugs.freebsd.org/bugzilla/> References: <bug-204426-16@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 --- Comment #59 from Robert Blayzor <rblayzor@inoc.net> --- Thinking about this a little, going out on a limb. The only thing that diff= ers on these servers compared to other diskless boot servers we have. (that use= the same read only NFS root) is they have a larger memory disks for "/var" when created from /etc/rc.initdiskless. /dev/md0 8.8M 3.8M 4.3M 47% /etc /dev/md1 457M 516K 420M 0% /var Because these are mail servers, /var may be a bit busier than on say DNS and web servers. (as /var/tmp is there, etc, temporary file writes from files b= eing scanned by viruses). I've never seen any "out of memory" errors or that mou= nt ever close to being anywhere near full; but I'm sure there are a lot of read/write going on. I know it's a stretch but it's the only thing I can think of that differs f= rom the other diskless servers that are setup the exact same way. This appears to be happening on only our mail servers, which consequently happen to be our busiest. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204426-16-umNKXZWXWM>