[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #1692 [Tor Relay]: No Events for SETCONF
#1692: No Events for SETCONF
-------------------------+--------------------------------------------------
Reporter: atagar | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: Tor Relay | Version:
Keywords: | Parent:
-------------------------+--------------------------------------------------
Comment(by nickm):
I've got no objections. I think, if there's an event for configuration
changes, it should tell you all configuration changes, including those
caused by HUP, not just those caused by a SETCONF.
By "produce an event at the INFO level" you mean a STATUS event? I hate
to cram more stuff into those, especially stuff that isn't related to the
status of the Tor server.
Or do you mean an INFO-level log? I'm fine with adding INFO or DEBUG-
level messages for this, but the format of individual log messages should
not be part of Tor's controller API. If there's any info that controllers
need to parse from the log, that's a gap in the API, not something to
emulate.
Instead, I think this ought to be a new event type, accessible via
SETEVENTS.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1692#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