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

Re: [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:
   Resolution:           |   Keywords:
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+-----------------

Comment (by karsten):

 That could work.  But I'm not sure if there's a platform-independent way
 to build it.  (One might argue that the current cron strategy is not
 platform-independent anyway, but hey.)

 Or maybe it's time to move away from having cron execute a new hourly Java
 process towards a single Java process that runs in a loop and sleeps after
 an execution until the next.  I just wonder how the service operator would
 learn when an execution fails, ideally via email.  Hmm.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13003#comment:2>
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