strange TERM signal
User on ticket #11560 experiences a TERM signal:
jul 05 09:12:59.619 [Notice] Tor v0.2.3.25 (git-17c24b3118224d65) running on Windows 7. jul 05 09:12:59.619 [Notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning jul 05 09:12:59.619 [Notice] Read configuration file "C:\Users\Jordi\Downloads\Tor Browser\Data\Tor\torrc". jul 05 09:12:59.619 [Notice] Initialized libevent version 2.0.21-stable using method win32. Good. jul 05 09:12:59.619 [Notice] Opening Socks listener on 127.0.0.1:9150 jul 05 09:12:59.619 [Notice] Opening Control listener on 127.0.0.1:9151 jul 05 09:12:59.833 [Notice] Parsing GEOIP file .\Data\Tor\geoip. jul 05 09:13:01.536 [Notice] No AES engine found; using AES_* functions. jul 05 09:13:01.536 [Notice] This OpenSSL has a good implementation of counter mode; using it. jul 05 09:13:01.536 [Notice] OpenSSL OpenSSL 1.0.0k 5 Feb 2013 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation jul 05 09:13:01.536 [Notice] Reloaded microdescriptor cache. Found 3896 descriptors. jul 05 09:13:01.536 [Notice] We now have enough directory information to build circuits. jul 05 09:13:01.536 [Notice] Bootstrapped 80%: Connecting to the Tor network. jul 05 09:13:01.536 [Notice] New control connection opened. jul 05 09:13:02.520 [Notice] Heartbeat: Tor's uptime is 0:00 hours, with 5 circuits open. I've sent 0 kB and received 0 kB. jul 05 09:13:02.520 [Notice] Bootstrapped 85%: Finishing handshake with first hop. jul 05 09:13:03.107 [Notice] Catching signal TERM, exiting cleanly.
Trac:
Username: Envite