From owner-freebsd-security@FreeBSD.ORG  Tue May 27 18:49:03 2014
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 66683D99
 for <freebsd-security@freebsd.org>; Tue, 27 May 2014 18:49:03 +0000 (UTC)
Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com
 [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 4F2EB28E7
 for <freebsd-security@freebsd.org>; Tue, 27 May 2014 18:49:02 +0000 (UTC)
Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1])
 by segfault.tristatelogic.com (Postfix) with ESMTP id A30F93ADD6
 for <freebsd-security@freebsd.org>; Tue, 27 May 2014 11:49:02 -0700 (PDT)
From: "Ronald F. Guilmette" <rfg@tristatelogic.com>
To: freebsd-security@freebsd.org
Subject: Re: NEVERMIND!
In-Reply-To: <201405271120.s4RBKiHp096461@catnip.dyslexicfish.net>
Date: Tue, 27 May 2014 11:49:02 -0700
Message-ID: <5918.1401216542@server1.tristatelogic.com>
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 18:49:03 -0000


In message <201405271120.s4RBKiHp096461@catnip.dyslexicfish.net>, 
Jamie Landeg-Jones <jamie@dyslexicfish.net> wrote:

>I've not actually used it, but I notice this in ports:
>
>/usr/ports/sysutils/socklog:
>
> | svlogd has a built in log file rotation based on file size, so there is no
> | need for any cron jobs or similar to rotate the logs. Log partitions can be
> | calculated properly.
> |
> | WWW: http://smarden.org/socklog/


Just skimming the man page for that, I have to agree that this looks like
an entirely adequate solution for the problem I posed.  (So clearly no need
for a PR.)