From owner-freebsd-current@FreeBSD.ORG Sun Dec 22 18:29:26 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 3CA28AC7 for ; Sun, 22 Dec 2013 18:29:26 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AB1261F95 for ; Sun, 22 Dec 2013 18:29:25 +0000 (UTC) Received: from [157.181.98.186] ([157.181.98.186]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0Lxxw4-1VP5Yo1ORI-015Lmk for ; Sun, 22 Dec 2013 19:29:18 +0100 Message-ID: <52B72F5A.7030700@gmx.com> Date: Sun, 22 Dec 2013 19:28:42 +0100 From: dt71@gmx.com User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:24.0) Gecko/20100101 Firefox/24.0 SeaMonkey/2.21 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=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:NKk77PdoHlpPFg2OBPBtuyioR6wodpVGZqeChH9+Aza1IaDX7R9 d5UpaZ4o/QBNl5DQQRaJA4O47KP3g93lLRjMfjuuqur3RhyLJFGw7JvgLzsZkJJz+JcSuj8 SNZnSIlJTc+OyGYz73USYno1InbgSI083OZCDNy1ytJC0wOq8hTjoNlZobQ0uMjva7GX5f8 wUqIeNdQAV4ZMl4mVJ0rw== Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list 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 18:29:26 -0000 Frank Seltzer wrote, On 12/22/2013 15:00: > Greg Rivers said: > > Do you really feel that strongly about it? Having a record of changes to > the system has always seemed like a feature to me... > > Baptiste Daroussin said: > > this has been done and activated for reason, first for lot of companies, it is important (PCI DSS requirement for example), secondly I receive tons of request to actiavte on by default while you are the first to request it off by default > > 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. > > My thought: > > Then why can't the messages about installed ports have it's own log file rather than /var/log/messages? > > As for this message: > > pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file > > Glen Barber replied: > > echo 'SYSLOG: no' >> /usr/local/etc/pkg.conf > > And Shane Ambler: > > now we can turn it off which I don't think we could before. All of this is mostly off-topic. I haven't had any opposition to logging. Instead, I originally thought that the PACKAGESITE spam was a result of a bug, because -- the spam appeared with a recent installworld; -- there were like 50 consecutive messages every now and then; -- I don't recall ever setting up any PACKAGESITE-related variables (the timestamp on the file is 2013-04-05, so I could be WRONG); -- I looked for pkg.conf (only) in /etc, and didn't find it there; -- neither of the UPDATING files contain instructions regarding pkg.conf; -- I haven't payed too much attention to HEADSUP mails in the last few weeks (what relevant things did I miss?). Why is pkg.conf in /usr/local/etc instead of /etc? By contrast, why does the sample configuration file (/usr/local/etc/pkg.conf.sample) contain a line that links to a file in /etc, namely "#PUBKEY : /etc/ssl/pkg.conf"? The pkg.conf of a -RELEASE won't be as "empty" as mine is currently (causing PACKAGESITE spam), will it? If not (obviously), then what will it look like?