Limiting the size of syslogd output files using options in syslog.conf
Rodney W. Grimes
freebsd-rwg at gndrsh.dnsmgr.net
Wed Jun 26 19:54:03 UTC 2019
> 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 at freebsd.org
More information about the freebsd-embedded
mailing list