Re: [tor-relays] tor-relays Digest, Vol 62, Issue 13

[stealth@xxxxxxxxxxxxxx]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 09 Mar 2016 01:16:18 +0000, you wrote:
>
> Message: 3
> Date: Wed, 9 Mar 2016 12:08:31 +1100
> From: Tim Wilson-Brown - teor <teor2345@xxxxxxxxx>
> To: tor-relays@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [tor-relays] Hibernation Expectations
> Message-ID: <6449D528-F52E-49E6-8331-0F3276365348@xxxxxxxxx>
> Content-Type: text/plain; charset="us-ascii"
>
>
> > On 9 Mar 2016, at 05:29, stealth@xxxxxxxxxxxxxx wrote:
> >
> > Signed PGP part
> > I am allocating 100gb of bandwidth up and down every day. When my
> > middle relay goes into hibernation, should I expect my stats to go
> > to hell? Should I also expect my flags my stable and guard flags to
> > be removed?
>
> Yes, but they'll come back eventually.
>
> >
> > If I reach my bandwidth restrictions 10 hours before it is reset,
> > is this the reason why the relay would lose guard and stable flags?
> > I may need to restrict my bandwidth to 60gb up and down as I only
> > have 3tb of bandwidth to donate on a monthly basis.
>
> This is another question we see frequently.
> Until we get a FAQ or wiki entry for it, I'd encourage you to search the list archives for previous answers.
>
> There are good reasons to run a relay that's always on.
> Then again, there are also good reasons to run a fast relay.
> If you're very close to your bandwidth cutoff, why not decrease it slightly, and run all the time?
>
> Tim

I have changed my AccountingMax to 60gb and my RelayBandwidthRate
to 5mb and my RelayBandwidthBurst to 10mb. I will monitor these
settings for the next couple of days to see, if I reach my
AccountingMax number. If I do reach the AccountingMax number then I
will reduce the RelayBandwidthRate and RelaybandwidthBurst down
until my server can run 24/7.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (MingW32)

iQIcBAEBAgAGBQJW4G4MAAoJEH1gNwhiMDZu8bsP/3j4GYhUKZMZbnm2+i+7XJ5C
vGWxQgHC/7bMe5zuQY7CjHuPZRjqNImbQTy8FPLb1NGKuutVS1RcQafDvTVBUJiL
a64dTCAAbf12AScSxCzhqgBpWQ1nW2mKRPTeGUOrkeCPgx3o/Cqby5U3fL0Hcy3R
lhrTWOlca3waJDnpNzlslMgXVLhoR+cspflKoi+NzFoanHDveipkcZEr65cIBoWJ
QlYcfH0CE1070W68DatwtNzyQW7Mm9bMULX8aWJQpjMIvd/GKZ6OGGysXjgLDbDN
x2b7/VcHuxNXaVJSbhdenoA2GoF1h02Sl9K1QUMVo46LqVfsJiZduSmvB4EJz9VA
KsMmTc3C51Mp3EgdH538gP9lfNA/PhT/1KrHFz9ILnC0sy9E8zxHzpk9+Lt7652/
PTaeVE0+1epAVG3namxaMLiK36gOUD4xuGi3UP18U2s7UzlaesEusSie6j+wHZid
/D3pQTE50Mj7eb4yxLziBU/DS3UB4FwhRphCKqnB/ZdJWbMZ88hAfwfcgxmTjvB0
7fZ6wtZDsdAqWPOTzRlkEVifS1ZcS0WgT2FGSmzBbUH7/hT9YTuKdHelUNrYBJy+
3b5A+6/kMCBUV0bJjiUirINATG0XJDGoYmSjFm/Z7ac/vfOh+TXzTwiG+yITJ1cA
FuaKL42rov2Ier2nWnYu
=BnNF
-----END PGP SIGNATURE-----

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays