Date: Sat, 30 Dec 2023 14:35:36 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 276023] security/logcheck: patch crontab to avoid duplicates Message-ID: <bug-276023-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276023 Bug ID: 276023 Summary: security/logcheck: patch crontab to avoid duplicates Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: yasu@freebsd.org Reporter: dvl@FreeBSD.org Assignee: yasu@freebsd.org Flags: maintainer-feedback?(yasu@freebsd.org) Created attachment 247359 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D247359&action= =3Dedit add patch to crontab In my 24 years of using logcheck, this problem has only arisen a few times. Sometimes, the log can grow very large. This happens when the host is heavi= ly loaded. Under those circumstances, logcheck does not complete before the ne= xt crontab starts. The attached patch introduces a /usr/bin/lockf call to avoid duplicate concurrent instances of logcheck. I've been running this within a dev instance of FreshPorts for about a week now. If this change seems to be generic, I hope it is helpful --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-276023-7788>