Remind authority operators that bandwidth files should be written atomcally

Tor reads bandwidth files when it's voting, around 50 minutes past every hour, and 20 minutes past hours when the consensus has failed.

We should recommend that authority operators generate and transfer bandwidth files between 5-15 or 35-45 minutes outside of 15-25 and 45-55 minutes past the hour. The best place for this might be in dir-spec or the bandwidth file spec.

changed milestone to %Tor: 0.3.5.x-final

added 035-removed-20180711 component::core tor/tor doc fast-fix milestone::Tor: 0.3.5.x-final owner::teor parent::26851 priority::medium resolution::implemented severity::normal status::closed torspec type::enhancement labels

It doesn't matter if the generator is remote or local, it still needs to be scheduled correctly.

Trac:
Description: Tor reads bandwidth files when it's voting, around 50 minutes past every hour, and 20 minutes past hours when the consensus has failed.

We should recommend that authority operators transfer bandwidth files between 5-15 or 35-45 minutes past the hour. The best place for this might be in dir-spec or the bandwidth file spec.

to

Tor reads bandwidth files when it's voting, around 50 minutes past every hour, and 20 minutes past hours when the consensus has failed.

We should recommend that authority operators generate and transfer bandwidth files between 5-15 or 35-45 minutes past the hour. The best place for this might be in dir-spec or the bandwidth file spec.

I thought to create a crontab file in the Debian package, But because would be needed for other distributions and it's essential to run sbws, i'm thinking now to add it to sbws repo. Created #26740 (moved) for it.

These tickets are being triaged out of 0.3.5. The ones marked "035-roadmap-proposed" may return.

Trac:
Milestone: Tor: 0.3.5.x-final to Tor: unspecified
Keywords: N/A deleted, 035-removed-20180711 added

Trac:
Keywords: N/A deleted, doc, fast-fix added
Status: new to assigned
Milestone: Tor: unspecified to Tor: 0.3.5.x-final
Owner: N/A to teor

The appropriate place for this documentation is in the man page, under the V3BandwidthsFile option. It's the place that authority operators are most likely to look when configuring a bandwidth authority.

Please see my branch ticket26702 on https://github.com/teor2345/tor.git

(We could also document this requirement in sbws, but sbws does atomic symlinks, so it's only important when using scp from a different host.)

Trac:
Description: Tor reads bandwidth files when it's voting, around 50 minutes past every hour, and 20 minutes past hours when the consensus has failed.

We should recommend that authority operators generate and transfer bandwidth files between 5-15 or 35-45 minutes past the hour. The best place for this might be in dir-spec or the bandwidth file spec.

to

Tor reads bandwidth files when it's voting, around 50 minutes past every hour, and 20 minutes past hours when the consensus has failed.

We should recommend that authority operators generate and transfer bandwidth files between 5-15 or 35-45 minutes outside of 15-25 and 45-55 minutes past the hour. The best place for this might be in dir-spec or the bandwidth file spec.
Status: assigned to needs_review

(We could also document this requirement in sbws, but sbws does atomic symlinks, so it's only important when using scp from a different host.)

I left a comment in #26740 (moved).

The distcheck travis CI on this doc-only branch failed, probably because of #26787 (moved).

lgtm

Trac:
Status: needs_review to merge_ready

I'm sorry; I can't find this branch. Are you sure it's where you say?

It seems it has been accidentally removed?

Replying to nickm:

I'm sorry; I can't find this branch. Are you sure it's where you say?

I forked torproject/tor yesterday so I could do pull requests. (GitHub doesn't support pull requests between repositories, unless they are in the same GitHub fork tree.) My old tor repository is at tor-old.

I have re-pushed the branch ticket26702 to ​https://github.com/teor2345/tor.git

I don't think this is what we should recommend. I think that instead we should recommend that these files be replaced atomically, via rename. How would that be?

Ok, I think that's better, I'll update all the docs at once.

Trac:
Parent: #25925 (moved) to #26851 (moved)
Status: merge_ready to needs_revision

Trac:
Summary: Remind authority operators that bandwidth files should be transferred outside the voting period to Remind authority operators that bandwidth files should be written atomcally

Please see my branch ticket26702-atomically on ​​https://github.com/teor2345/tor.git

Trac:
Status: needs_revision to merge_ready

The travis CI failed for this doc-only branch due to #26787 (moved)

The appveyor CI failed for this doc-only branch, I opened #26853 (moved) to fix it.

Merged!

Trac:
Status: merge_ready to closed
Resolution: N/A to implemented