#19720: CollecTor should be re-configurable without restart -------------------------------+--------------------------------- Reporter: iwakeh | Owner: iwakeh Type: enhancement | Status: needs_review Priority: High | Milestone: CollecTor 1.0.0 Component: Metrics/CollecTor | Version: Severity: Normal | Resolution: Keywords: ctip | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -------------------------------+---------------------------------
Comment (by iwakeh): Replying to [comment:11 karsten]: > weasel notes on IRC that services that auto-check if their configuration files change are extremely suspicious. He says that a service should require some signal to re-read its configuration file. > > Let's think again if we can implement something like that. I briefly looked whether we can catch a SIGHUP signal, but that doesn't seem very platform independent. Another way would be to touch a "reload-config" file of some sort and have the current thread check whether that exists. But there are probably better ways. Hmmmmm. I didn't notice that before answering the previous comment. So: Well, how much of a 'service' the different modules in CollecTor constitute is surely debatable. Therefor two questions: * What is the use-case that justifies here when having to edit and then signal a change? * Isn't it worse in this particular case to forget the second step? Anyway, if we decide to have the two-level re-config, one can always use other Java ways of 'signalling' the application. But that will be a future release. -- Ticket URL: <https://troodi.torproject.org/projects/tor/ticket/19720#comment:13> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs