From owner-freebsd-current@FreeBSD.ORG Sun Dec 22 19:53:22 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 44224FC3 for ; Sun, 22 Dec 2013 19:53:22 +0000 (UTC) Received: from rush.bluerosetech.com (rush.bluerosetech.com [IPv6:2607:fc50:1000:9b00::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0BF21149F for ; Sun, 22 Dec 2013 19:53:21 +0000 (UTC) Received: from chombo.houseloki.net (c-71-236-222-167.hsd1.wa.comcast.net [71.236.222.167]) by rush.bluerosetech.com (Postfix) with ESMTPSA id 91D331146C; Sun, 22 Dec 2013 11:53:20 -0800 (PST) Received: from [IPv6:2601:7:16c0:b50:1d80:290c:433a:8307] (unknown [IPv6:2601:7:16c0:b50:1d80:290c:433a:8307]) by chombo.houseloki.net (Postfix) with ESMTPSA id 71098B46; Sun, 22 Dec 2013 11:53:18 -0800 (PST) Message-ID: <52B7432D.3070106@bluerosetech.com> Date: Sun, 22 Dec 2013 11:53:17 -0800 From: Darren Pilgrim User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Frank Seltzer , Steve Kargl Subject: Re: PACKAGESITE spam References: <52B5DF8C.5050204@gmx.com> <20131221200538.GA60827@troutmask.apl.washington.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: freebsd-current List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Dec 2013 19:53:22 -0000 On 12/22/2013 6:00 AM, Frank Seltzer wrote: > Adrian Chadd said: > > The point is that some people like an audit trail. The audit trail for > some people involves remote logging of syslog messages to a log host. > This would include when packages are installed. There are two more: 1. When a port was deinstalled 2. History of a port (previous installs/deinstalls) For example, my logs have: Sep 9 16:05:28 chombo pkg-static: postfix-2.10.0,1 deinstalled Sep 9 16:05:36 chombo pkg-static: postfix-2.10.0,1 installed Nov 30 00:25:02 chombo pkg: postfix-2.10.0,1 deinstalled Nov 30 00:25:09 chombo pkg-static: postfix-2.10.2,1 installed Which tells me I recompiled postfix on Sept 9 (this would have been when I changed it over to openssl from ports) and updated it to 2.10.2 on Nov 30 using portmaster. How do I know that? Because of that deinstall log. When you use `pkg install` to upgrade a port, you get something like this: Jul 10 23:06:40 chombo pkg-static: ca_root_nss-3.15.1 installed Nov 29 15:04:52 chombo pkg: ca_root_nss reinstalled: 3.15.2_1 That information does not exist in the pkg database. > My thought: > > Then why can't the messages about installed ports have it's own log file > rather than /var/log/messages? I have never understood why anyone would enable the use of syslog without also providing a way of specifying the facility and level. I'd much rather do stuff like this: local0.* /var/log/dovecot.log local1.* /var/log/postgres.log local2.* /var/log/php-fpm.log