[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-bugs] #13003 [Onionoo]: Figure out a better strategy to avoid concurrent Onionoo executions



#13003: Figure out a better strategy to avoid concurrent Onionoo executions
---------------------+---------------------
 Reporter:  karsten  |          Owner:
     Type:  defect   |         Status:  new
 Priority:  normal   |      Milestone:
Component:  Onionoo  |        Version:
 Keywords:           |  Actual Points:
Parent ID:           |         Points:
---------------------+---------------------
 The current strategy for the hourly cronjob to avoid concurrent executions
 is to write a lock file at startup and delete it upon termination.  And if
 there's already such a file at startup the cronjob doesn't start.

 This strategy works fine if there's a live process not succeeding on time.
 It fails pretty badly if a process died, because subsequent runs won't
 start without human intervention.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13003>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs