From owner-freebsd-ports-bugs@FreeBSD.ORG Mon Dec 19 17:30:11 2011 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A977C106564A for ; Mon, 19 Dec 2011 17:30:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 97BE88FC08 for ; Mon, 19 Dec 2011 17:30:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBJHUBtR064170 for ; Mon, 19 Dec 2011 17:30:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBJHUBv4064165; Mon, 19 Dec 2011 17:30:11 GMT (envelope-from gnats) Date: Mon, 19 Dec 2011 17:30:11 GMT Message-Id: <201112191730.pBJHUBv4064165@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Mij Cc: Subject: Re: ports/163126: security/sshguard changed from syslog.conf to daemon boot script X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mij List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2011 17:30:11 -0000 The following reply was made to PR ports/163126; it has been noted by GNATS. From: Mij To: bug-followup@FreeBSD.org, freebsd@akruijff.dds.nl Cc: Subject: Re: ports/163126: security/sshguard changed from syslog.conf to daemon boot script Date: Mon, 19 Dec 2011 18:12:44 +0100 I can see a few of reasons why people prefer boot scripts to syslog: * when run by syslog, every log rotation restarts sshguard, and so blocked addresses are reset. * it's simpler to maintain: if you want to stop/restart sshguard, syslog.conf is not where you'd look out of intuition. * it's more flexible. Many use sshguard to protect additional services that do not log through syslog. As to automatic upgrades, I wouldn't feel "stuck" with syslog or complex backward-compatibility knobs. A note in /usr/ports/UPDATING should do. I'll review this patch next weeks.