From owner-freebsd-current@FreeBSD.ORG Sun Dec 22 14:55:29 2013 Return-Path: Delivered-To: freebsd-current@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 A18AC684 for ; Sun, 22 Dec 2013 14:55:29 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2F8B9120A for ; Sun, 22 Dec 2013 14:55:28 +0000 (UTC) Received: from [192.168.0.100] ([87.139.233.65]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0M8edX-1VYFhd3UIN-00wF9a for ; Sun, 22 Dec 2013 15:55:27 +0100 Message-ID: <52B6FD68.5080808@gmx.de> Date: Sun, 22 Dec 2013 15:55:36 +0100 From: olli hauer User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Frank Seltzer , "freebsd-current@freebsd.org" Subject: Re: PACKAGESITE spam References: <52B5DF8C.5050204@gmx.com> <20131221200538.GA60827@troutmask.apl.washington.edu> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:yErR7yMtUFL6SaMI497NC/9IZuI8Rvrtvv0OFffNLVVePCJmHC1 aqLA0D8qsUMeaR+8gYQ8hkWZKe+vG9sBTO4TwE53k6d6fRJwQ2KmS+P/RoQZOySFiJGVe9X zQ0QqtCiP5+dlrXnh+dBPV2AIXAQZ5fOcifCJ2Lov9SInXT+gRobXeVIylodi4EOXQ8kOYm q30kfrq27OG7yngFOAXSw== Cc: dt71@gmx.com, Steve Kargl 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 14:55:29 -0000 On 2013-12-22 15:00, Frank Seltzer wrote: > > On Sat, 21 Dec 2013, Steve Kargl wrote: > >> On Sat, Dec 21, 2013 at 07:35:56PM +0100, dt71@gmx.com wrote: >>> I've just installed a very recent -CURRENT, and now I'm performing a big portupgrade procedure. I get the following message spammed a lot: >>> >>> pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file >> >> Yeah, I noticed that spam along with the spam that is being >> spewed to /var/log/messaage, e.g., >> >> Dec 21 10:27:28 laptop-kargl pkg-static: libwpg-0.2.2 installed >> Dec 21 10:31:15 laptop-kargl pkg-static: libcdr-0.0.14 installed >> Dec 21 10:32:35 laptop-kargl pkg-static: openjpeg-1.5.0_2 installed >> Dec 21 10:38:33 laptop-kargl pkg-static: poppler-data-0.4.6 installed >> Dec 21 10:39:48 laptop-kargl pkg-static: poppler-0.22.2 installed >> Dec 21 10:40:32 laptop-kargl pkg-static: ilmbase-2.1.0 installed >> Dec 21 10:44:28 laptop-kargl pkg-static: OpenEXR-2.1.0_1 installed >> Dec 21 10:47:36 laptop-kargl pkg-static: vigra-1.9.0_4 installed >> Dec 21 10:51:00 laptop-kargl pkg-static: lp_solve-5.5.2.0 installed >> >> Can you (portmgr) please mute these messages? >> >> -- >> Steve > > This received several responses. > > 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. > > Me again: > > Where is this documented? > > /root # man pkg.conf > No manual entry for pkg.conf Hm, on all my systems I have a man page for pkg.conf Here is the referenced passage from man 5 pkg.conf OPTIONS The following options can be defined in pkg.conf: ... SYSLOG: boolean This option is enabled by default, log all the installation/deinstallation/upgrade oper- ation via syslog(3) What I agree is having it would be nice to have dedicated syslog (like yum.log) instead /var/log/messages since this is already spammed by most every process. -- olli