Date: Mon, 26 May 2014 16:11:52 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: "Ronald F. Guilmette" <rfg@tristatelogic.com> Cc: freebsd-security@freebsd.org Subject: Re: NEVERMIND! Message-ID: <86r43gr5nb.fsf@nine.des.no> In-Reply-To: <2218.1401075427@server1.tristatelogic.com> (Ronald F. Guilmette's message of "Sun, 25 May 2014 20:37:07 -0700") References: <2218.1401075427@server1.tristatelogic.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Ronald F. Guilmette" <rfg@tristatelogic.com> writes: > I forgot that newsyslog(8) should limit the size of /var/log/messages, and > that as long as you limit the size of that to a reasnable value, and as > long as you have newsyslog(8) only keeping a finite & reasonable number > of "rotated out" copies, then /var won't fill up. It can still happen, since newsyslog only runs once per hour. If /var fills up between two newsyslog runs, there is no guarantee that the space freed up by deleting the oldest logs is sufficient to compress the newest log. The only way to really handle this issue would be to fold newsyslog into syslog. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86r43gr5nb.fsf>