Well, can be hard to say just looking at that number. Linux is not Windows.. it
doesn't have to reboot every time it's patched.
A tor op
Originalmeddelande
På 4 okt. 2019 14:35, Steve Snyder < swsny...@snydernet.net> skrev:
On 10/4/19 7:39 AM, li...@for-privacy.net wrote:
> On
I also do -not- get an answer @ that DNS but other domains resolve
https://puu.sh/Ep4Ws/150c13aef7.png
Matt Westfall
President & CIO
ECAN Solutions, Inc.
Everything Computers and Networks
804.592.1672
-- Original Message --
From: "Geoff Down"
To: tor-relays@lists.torproject.org
Sent:
On Mon, Oct 07, 2019 at 04:56:32PM +0200, Volker Mink wrote:
> I am running an OBFS4 Bridge at home for a while now.
>
> But everytime im looking in the logs it says
> # [notice] Bootstrapped 0%: Starting
Hi Volker,
Three suggestions:
(A) Upgrade to a newer version of Tor. Tor 0.2.9.x is way wa
After a fresh installation syslog is full with entries like this:
Oct 7 23:05:09 pi-hole systemd[1]: tor@default.service: Failed with result 'signal'.
Oct 7 23:05:09 pi-hole systemd[1]: tor@default.service: Service hold-off time over, scheduling restart.
Oct 7 23:05:09 pi-hole systemd[1]:
On 04.10.2019 23:33, a tor op wrote:
Well, can be hard to say just looking at that number. Linux is not
Windows.. it doesn't have to reboot every time it's patched.
I'm sure every GNU / Linux distri had several kernel upgrades in that
time ;-)
Note: install unattended upgrades, nullmailer and
On Mon, Oct 07, 2019 at 11:09:53PM +0200, Volker Mink wrote:
> After a fresh installation syslog is full with entries like this:
[...]
> Oct 7 23:05:09 pi-hole systemd[1]: Failed to start Anonymizing overlay
> network for TCP.
My next guess is that you have an old-style raspbian, with an old
arm
