Thank you!
> On Nov 1, 2016, at 05:17, Karsten Loesing wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi everyone,
>
> can you check once again?
>
> There was a problem with the data-collecting service that silently
> died on October 30 at around 23:00 UTC. I have been work
On 1 November 2016 at 10:16, Karsten Loesing wrote:
> Hi everyone,
>
> can you check once again?
>
> There was a problem with the data-collecting service that silently
> died on October 30 at around 23:00 UTC. I have been working on that
> problem for an hour or two, and it should be resolved by
Works, thank you very much!
2016-11-01 11:16 GMT+01:00 Karsten Loesing :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi everyone,
>
> can you check once again?
>
> There was a problem with the data-collecting service that silently
> died on October 30 at around 23:00 UTC. I have been
On 2016-11-01 at 11:16, Karsten Loesing wrote:
> Hi everyone,
>
> can you check once again?
>
> There was a problem with the data-collecting service that silently
> died on October 30 at around 23:00 UTC. I have been working on that
> problem for an hour or two, and it should be resolved by now.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi everyone,
can you check once again?
There was a problem with the data-collecting service that silently
died on October 30 at around 23:00 UTC. I have been working on that
problem for an hour or two, and it should be resolved by now. Please
try
Same here.
Sent from my iPad
> On 1 Nov 2016, at 10:42, Michael Armbruster wrote:
>
>> On 2016-11-01 at 10:34, Pascal Terjan wrote:
>> For example
>> https://atlas.torproject.org/#details/20462CBA5DA4C2D963567D17D0B7249718114A68
>> says uptime is 12 days and current version is 0.2.6.10 but I
On 2016-11-01 at 10:34, Pascal Terjan wrote:
> For example
> https://atlas.torproject.org/#details/20462CBA5DA4C2D963567D17D0B7249718114A68
> says uptime is 12 days and current version is 0.2.6.10 but I upgraded
> the machine and updated tor to 0.2.8.9 over a day ago:
>
I currently have problems
For example
https://atlas.torproject.org/#details/20462CBA5DA4C2D963567D17D0B7249718114A68
says uptime is 12 days and current version is 0.2.6.10 but I upgraded
the machine and updated tor to 0.2.8.9 over a day ago:
# uptime
09:30:50 up 1 day, 8:32, 1 user, load average: 0.68, 0.81, 0.88
# ps
On Sat, Jan 24, 2015 at 3:16 PM, cacahuatl wrote:
> Most of the network is under-utilised guards and middle nodes, hidden
> services don't stress exits, which are the limited resource.
Exits can and do serve in all the other node roles too.
I don't think there has yet been a study to determine th
hello Moritz, thanks for your reply,
I take the smallest offer in vps, to decrease the swapping and consum of
ram i have to decrease RelayBandwidthRate?
for the moment it's at 1000 KB and the burst at 1500 KB, it's better to
put it to 500 KB ? that will give fluidity to the machine?
but if i l
hi,
thanks for your reply, i always make confusion with that.
and tkans for iftop -PB before i just use iftop
Le 05.07.2013 21:03, Jack Lu a écrit :
iftop will show kilobits per second by default, while the graph in the
page you linked is in kilobytes per second. Are you using iftop -PB so
tha
Hi Armand,
Thank you for running an exit. 128 MB RAM is low, I usually recommend at
least 256 MB RAM. If you want to push more (and if your line allows it),
you need more RAM.
I would say don't worry about the difference in display.
On 07.07.2013 04:40, Armand wrote:
>
>
> Sent from my Cricket
Sent from my Cricket smart phone
ma...@mykolab.com wrote:
>hello,
>i'm running an exit node from 2 or 3 month, in UA, on a vps, xeon 2650
>2Ghz, 128mb RAM, debian 6
>tor v0.2.3.25-1
>
>
>on atlas there is some stat on those days it's seem to be at max 100Kb/s
>
>
>
>
>
>
>
>//atlas
Sent from my Cricket smart phone
ma...@mykolab.com wrote:
>hello,
>i'm running an exit node from 2 or 3 month, in UA, on a vps, xeon 2650
>2Ghz, 128mb RAM, debian 6
>tor v0.2.3.25-1
>
>
>on atlas there is some stat on those days it's seem to be at max 100Kb/s
>
>
>
>
>
>
>
>//atlas
iftop will show kilobits per second by default, while the graph in the
page you linked is in kilobytes per second. Are you using iftop -PB so
that iftop shows bytes instead of bits?
(Note that Kb/s means kilobits per second and KB/s means kilobytes per second.)
On 7/5/13, ma...@mykolab.com wrote
hello,
i'm running an exit node from 2 or 3 month, in UA, on a vps, xeon 2650
2Ghz, 128mb RAM, debian 6
tor v0.2.3.25-1
on atlas there is some stat on those days it's seem to be at max 100Kb/s
//atlas.torproject.org/#details/62C3FB37C44555E55A62BBD7CDDD97FE4894F317
but on arm or
On 8/3/12 12:10 PM, Michael Zeltner wrote:
> Excerpts from Karsten Loesing's message of 2012-08-01 16:13:41 +0200:
>> https://gitweb.torproject.org/karsten/metrics-tasks.git/shortlog/refs/heads/task-6329-family
>>
>> If you like it, I'll squash our two commits, making you the commit
>> author, and
Excerpts from Karsten Loesing's message of 2012-08-01 16:13:41 +0200:
> https://gitweb.torproject.org/karsten/metrics-tasks.git/shortlog/refs/heads/task-6329-family
>
> If you like it, I'll squash our two commits, making you the commit
> author, and will push it to the official repo.
The changes
On 7/28/12 9:30 PM, Michael Zeltner wrote:
>> Thanks for sending the patch! Most of it looks good, but I took out the
>> --family-for-fp option which, I think, isn't entirely correct. This
>> option looks for relays having the given fingerprint in their family
>> line, but it doesn't cross-check
Excerpts from Karsten Loesing's message of 2012-07-23 08:59:20 +0200:
> I'm cc'ing tor-relays for the discussion here, because I figured if
> you're okay with sharing the patch, you're probably also okay with a
> public discussion of it. :)
Indeed!
> Thanks for sending the patch! Most of it look
Hi Michael,
I'm cc'ing tor-relays for the discussion here, because I figured if
you're okay with sharing the patch, you're probably also okay with a
public discussion of it. :)
On 7/21/12 4:19 PM, Michael Zeltner wrote:
> Hi Karsten,
>
> On my way out, and I would otherwise forget but here you g
21 matches
Mail list logo
