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

Re: [tor-bugs] #16296 [Onionoo]: Implement lock file in a more robust way

#16296: Implement lock file in a more robust way
-------------------------+-----------------
     Reporter:  karsten  |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:
    Component:  Onionoo  |    Version:
   Resolution:           |   Keywords:
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+-----------------

Comment (by leeroy):

 How robust does it need to be? I ran into this when I '!^C' on the updater
 which left the lock file unreleased. This could perhaps also be solved by
 adding a shutdown hook on the updater's
 [https://docs.oracle.com/javase/7/docs/api/java/lang/Runtime.html#addShutdownHook(java.lang.Thread)
 runtime]. Maybe try a snippet of both? Neither option is going to catch
 the unexpected system crash/reset. If you need it to be bulletproof it
 might be worthwhile to check the pid of running java VM (in addition).

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