[tor-bugs] #16296 [Onionoo]: Implement lock file in a more robust way
Tor Bug Tracker & Wiki
blackhole at torproject.org
Mon Jun 15 09:10:46 UTC 2015
#16296: Implement lock file in a more robust way
-------------------------+--------------------------
Reporter: karsten | Owner:
Type: defect | Status: needs_review
Priority: normal | Milestone:
Component: Onionoo | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
-------------------------+--------------------------
Comment (by karsten):
Oh wow, that's quite some code there for preventing concurrent executions.
Please don't hate me for this suggestion, but what do you think of making
the periodic updater the normal mode of operation and getting rid of the
lock file entirely?
Want to take a look at #13600 and the branch there? Note that it
currently uses a lock file, but I could see us removing that. Service
operators would then be responsible for not starting two instances of the
updater concurrently. If there's no risk anymore that two cron runs get
in each other's way, this seems like a reasonable assumption.
Thoughts?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16296#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list