Date: Wed, 26 Jun 2019 12:53:58 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> To: Karl Denninger <karl@denninger.net> Cc: freebsd-embedded@freebsd.org Subject: Re: Limiting the size of syslogd output files using options in syslog.conf Message-ID: <201906261953.x5QJrwgE055994@gndrsh.dnsmgr.net> In-Reply-To: <3feff28d-0b91-a6fc-b0e9-161d3d315a78@denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 6/26/2019 09:49, Ian Lepore wrote: > > > > Over the years we've upstreamed every freebsd customization we've ever > > done at $work except this one. The only reason I've been carrying this > > one local mod is because it seemed too specialized to be useful to > > anyone else. Then yesterday someone working on an embedded-system > > product asked me on irc how to solve the problem of unexpected log > > spewage, so I offered the solution we've been using. > > > > -- Ian > > Yep -- this is a small corner case /but if it happens /in the embedded > world (and I've had it happen) it's a five-alarm pain in the neck. > > I'm in favor for that reason, and I can't see how having it there hurts > someone that doesn't use it. I would not restrict this to an embedded system problem, our default sizes and rotate rates on even /var/log/messages require a tiny 600kbhyte log event and your good info is gone... I always tweak my newsyslog.conf file as our defaults are near useless for post failure analysys. > Karl Denninger -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201906261953.x5QJrwgE055994>