From owner-freebsd-embedded@freebsd.org Wed Jun 26 14:54:33 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 E4F3E15CA45F for ; Wed, 26 Jun 2019 14:54:32 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2m.ore.mailhop.org (outbound2m.ore.mailhop.org [54.149.155.156]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2387570F49 for ; Wed, 26 Jun 2019 14:54:31 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1561560865; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=MCsNhefG3iLH5NGDVzFhLaLfu7jXc9Ou7SzgzmD7+wvvO2bvMSTh5fInrnSrl34P0EHdGBAQiW0Y+ XkNbHzF7VeI3gkJ5adUy107kBzmz6ZosjcdIzpxoeJvh5yqnCuMvsVNrtGNgYp1xgvDoT2d8yeP3rP VIv8GmBDRBAUHhdfs6Txbb8o6ALqCWDgu4GWT6PLpGkD8PUulygecurF+9wHhtagMbuoidTYtby8hm 6kBiRfU2FTLxbdA8tTqJBGENzLvInxdMqNJtitoaWHJZqHCUJ5AeqDVugbj9WdZHSrgzuXzyypT3vz uEf3zjLyHw8cP08d0zq9Y0paBYsW2VA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=3nL4t5dWWVna4zBaWNEvII39UnwWgBYtk1N5wXDFIWo=; b=f9G8c4OoDwEy5wnk8+y5g4IpQes9alwHgNsxsQ8ctXFKDP5P5cmP0AX+nf2y2zprDMcrDEQGNfVba V0mzXNC2C3Lp2II932jFahJeyciT+tYXcIYA+GDWqy5TTMAv/FzpfxVAQTEaAS5XRrCApjsKG824V0 TfoEJ8Pbr9fWQWC/zNR6gPK9Jusaxrg+xDT9LkHe6N9GltPWZaqFSwdUPbBU11uuZll84sH20VR3iJ ov5yOhwvzepYVd+95quPnVkKakgZ53miCbZGBPQVeDY6F6Y89brzUtCZs1M1eKI4+0/tkoJ+YMBJyj M/TD5BP4ge7jywhWP8qUhmIMQ8p8jCg== ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=3nL4t5dWWVna4zBaWNEvII39UnwWgBYtk1N5wXDFIWo=; b=vBUEhpdWH4ighJPiaY0YVcdmgla1A63UjT3bdm1ckDHw0m2PprXi1F2M4ODJSJMRxeyeO6FabrBOa Gyuv4mTrEo8CLWSK2nfQR8oJD8fQT4WyI5PuqO3xKRdGgpoxyVVtk+0otLP3S/m7Q1Z0uYoydNkMoL X9BxD87oHaWQnmEdaGzJSn0yrC8Mn8NAXFq17G7N7Ha79gy9IIb6KhLP3/Vm3CT3umh9mJ3Kwamw05 mx7PKVzFK0fP1l8jfM88Alyx9YPJqsdt+fGtmIuRWv01+kQTByiNyJbMGtels4Sw9kGf6lfmfVCD3t 0u/PuJABTwFksRFNeJXf00RRp6riL/A== X-MHO-RoutePath: aGlwcGll X-MHO-User: 49388d28-9822-11e9-8d98-0b538189c249 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id 49388d28-9822-11e9-8d98-0b538189c249; Wed, 26 Jun 2019 14:54:24 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x5QEsNN1051017; Wed, 26 Jun 2019 08:54:23 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: Limiting the size of syslogd output files using options in syslog.conf From: Ian Lepore To: Poul-Henning Kamp Cc: freebsd-hackers@freebsd.org, freebsd-embedded@freebsd.org Date: Wed, 26 Jun 2019 08:54:23 -0600 In-Reply-To: <30082.1561525622@critter.freebsd.dk> References: <30082.1561525622@critter.freebsd.dk> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 2387570F49 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.99 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.992,0]; ASN(0.00)[asn:16509, ipnet:54.148.0.0/15, country:US] 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 14:54:33 -0000 On Wed, 2019-06-26 at 05:07 +0000, Poul-Henning Kamp wrote: > -------- > In message < > bf597c3830ebabbef6ac422a5d648e1eed13fac5.camel@freebsd.org>, Ian Le > pore writes: > > I've posted a review of a small syslogd change which lets you set a > > limit on the size of syslogd output files in /etc/syslog.conf. The > > idea is to prevent filling up a filesystem on emmc or sdcard or > > other > > small storage device on an embedded system with unexpected logging > > triggered by some error or failing hardware. > > You should consider fifolog(1) in such environments. > > fifolog looks pretty cool and I had no idea it existed, so thanks for the pointer; I may find useful things to do with it. But for the problem of unexpected syslog spewage it has exactly the same problem as running newsyslog very frequently: by design it discards the information you most want preserved (the triggering event that led to unexpected log spewage) while carefully preserving all the following noise which is typically more about symptoms rather than causes of the problem. -- Ian