Date: Tue, 25 Jun 2019 16:06:30 -0700 From: Michael Sierchio <kudzu@tenebras.com> To: Ian Lepore <ian@freebsd.org> Cc: freebsd-embedded@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Limiting the size of syslogd output files using options in syslog.conf Message-ID: <CAHu1Y72_hKcTcAvohsJOLvwwh2y3mseJGYJQbB0DqxkioBc_iA@mail.gmail.com> In-Reply-To: <bf597c3830ebabbef6ac422a5d648e1eed13fac5.camel@freebsd.org> References: <bf597c3830ebabbef6ac422a5d648e1eed13fac5.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Apologies, but I don't understand the point of this at all. I object especially to idea of patching syslogd when EVERYTHING you seek can be accomplished with appropriate settings in /etc/newsyslog.conf and changing its entry in /etc/crontab to run more frequently. You can control the size and number of files there. You can also do remote syslog. Do you need to rotate logs more than once per minute? On Tue, Jun 25, 2019 at 3:25 PM Ian Lepore <ian@freebsd.org> wrote: > 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. > > If you're interested, please see the review at > > https://reviews.freebsd.org/D20764 > > -- Ian > > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.or= g > " > --=20 "Well," Brahm=C4=81 said, "even after ten thousand explanations, a fool is = no wiser, but an intelligent person requires only two thousand five hundred." - The Mah=C4=81bh=C4=81rata
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHu1Y72_hKcTcAvohsJOLvwwh2y3mseJGYJQbB0DqxkioBc_iA>