From owner-freebsd-ports@freebsd.org Tue Feb 9 05:18:03 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A2CEAA26F9; Tue, 9 Feb 2016 05:18:03 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CF6211BEE; Tue, 9 Feb 2016 05:18:02 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-244-25.knology.net [216.186.244.25] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id u195HxEd019732 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 8 Feb 2016 23:18:00 -0600 Subject: Re: tor logging References: <56B90930.3000802@hiwaay.net> <20160208224644.f696fce2.freebsd@edvax.de> Cc: FreeBSD ports list !!!! , FreeBSD Questions !!!! From: "William A. Mahaffey III" Message-ID: <56B97687.8050703@hiwaay.net> Date: Mon, 8 Feb 2016 23:23:29 -0553.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <20160208224644.f696fce2.freebsd@edvax.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Feb 2016 05:18:03 -0000 On 02/08/16 15:52, Polytropon wrote: > On Mon, 8 Feb 2016 15:36:58 -0553.75, William A. Mahaffey III wrote: >> My torrc >> files seems to indicate logging to /usr/local/var/log/tor, but no such >> file or directory. > Create this directory subtree and an empty log file. Then check > if it will actually be used for logging - if that is what the > torrc file indicates. Otherwise, set a different logging file, > but make sure it does actually exist. > > Further review seems to indicate use of the built-in syslog system: [root@kabini1, /etc, 11:17:03pm] 477 % grep log /usr/local/etc/tor/torrc ## may provide sensitive information to an attacker who obtains the logs. ## Send all messages of level 'notice' or higher to /usr/local/var/log/tor/notices.log #Log notice file /usr/local/var/log/tor/notices.log ## Send every possible message to /usr/local/var/log/tor/debug.log #Log debug file /usr/local/var/log/tor/debug.log ## Use the system log instead of Tor's logfiles #Log notice syslog [root@kabini1, /etc, 11:17:08pm] 478 % grep log /usr/local/etc/tor/torrc.default ## may provide sensitive information to an attacker who obtains the logs. ## Send all messages of level 'notice' or higher to /usr/local/var/log/tor/notices.log #Log notice file /usr/local/var/log/tor/notices.log ## Send every possible message to /usr/local/var/log/tor/debug.log #Log debug file /usr/local/var/log/tor/debug.log ## Use the system log instead of Tor's logfiles Log notice syslog [root@kabini1, /etc, 11:17:10pm] 479 % lltr /var/log/tor* -rw-r----- 1 _tor _tor 230140 Jan 21 2015 /var/log/tor.4.bz2 -rw-r----- 1 _tor _tor 122109 Feb 23 2015 /var/log/tor.3.bz2 -rw-r----- 1 _tor _tor 126723 Mar 30 2015 /var/log/tor.2.bz2 -rw-r----- 1 _tor _tor 147674 May 28 2015 /var/log/tor.1.bz2 -rw-r----- 1 _tor _tor 166094 Dec 3 00:06 /var/log/tor.0.bz2 [root@kabini1, /etc, 11:17:19pm] 480 % In the past (before last upgrade) tor logged to a file in /var/log, see above. Afterward, ???? There was a directory named /var/log/tor, owned _tor:_tor, but it was empty & I removed it after a week or so & re-created it & restarted tor. It restarts OK & seems to be working OK, just no logging. Has the amount of logging changed from a couple of months ago ? -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.