From owner-freebsd-embedded@freebsd.org Wed Jun 26 19:54:02 2019 Return-Path: Delivered-To: freebsd-embedded@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CEA4A15D0989 for ; Wed, 26 Jun 2019 19:54:02 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2B818855A7 for ; Wed, 26 Jun 2019 19:54:02 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x5QJrwrH055995; Wed, 26 Jun 2019 12:53:58 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x5QJrwgE055994; Wed, 26 Jun 2019 12:53:58 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201906261953.x5QJrwgE055994@gndrsh.dnsmgr.net> Subject: Re: Limiting the size of syslogd output files using options in syslog.conf In-Reply-To: <3feff28d-0b91-a6fc-b0e9-161d3d315a78@denninger.net> To: Karl Denninger Date: Wed, 26 Jun 2019 12:53:58 -0700 (PDT) CC: freebsd-embedded@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 2B818855A7 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [2.13 / 15.00]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; MX_GOOD(-0.01)[cached: gndrsh.dnsmgr.net]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.10)[-0.105,0]; FROM_HAS_DN(0.00)[]; NEURAL_SPAM_SHORT(0.86)[0.860,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.45)[0.447,0]; R_SPF_NA(0.00)[]; IP_SCORE(0.04)[ip: (0.14), ipnet: 69.59.192.0/19(0.07), asn: 13868(0.05), country: US(-0.06)] X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jun 2019 19:54:03 -0000 > 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