On 02.07.2017 00:03, Paw Møller wrote:
> it seems the main torrc is not read, so maybe this is just an fancy way
> of doing the "old"
> /usr/sbin/tor -f /usr/local/etc/torrc1
> /usr/sbin/tor -f /usr/local/etc/torrc2
> ...
> with separate configurationfiles and datadir?
Yes.
> I have a few extra
On Mon, Jul 03, 2017 at 09:58:02PM +0200, Felix wrote:
> [warn] channelpadding_compute_time_until_pad_for_netflow: Bug: Channel
> padding timeout scheduled 212ms in the past. Did the monotonic clock just
> jump? (on Tor 0.3.1.3-alpha dc47d936d47ffc25)
https://bugs.torproject.org/22212
> and
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/03/2017 09:58 PM, Felix wrote:
> Switching to 3.1.4a might fix it ?
Doubt,
got it today too (just once till now) at 0.3.1.4-alpha
- --
Toralf
PGP C4EACDDE 0076E94E
-BEGIN PGP SIGNATURE-
iI0EAREIADUWIQQaN2+ZSp0CbxPiTc/E6s3eAHbpTgUCWV
Hi everybody
On 3.1.3a there are quiet some log entries like 10 per day and relay,
more cicuits - more entries:
[warn] channelpadding_compute_time_until_pad_for_netflow: Bug: Channel
padding timeout scheduled 212ms in the past. Did the monotonic clock
just jump? (on Tor 0.3.1.3-alpha dc47d93
On Mon, Jun 5, 2017 at 9:01 AM, Nick Mathewson wrote:
> Hi!
>
> This is a reminder that we will not be making new releases for the
> 0.2.4, 0.2.6, or 0.2.7 release series after 1 August 2017. If you are
> running one of those series, please make a plan to upgrade some time
> before then!
>
> 0.2.