GETINFO requests trigger conn_read_callback events
GETINFO requests are triggering the following DEBUG runlevel events: "conn_read_callback(): socket 15 wants to read.". Is this intentional?
This traces back to the 'connection_add' function of 'or/main.c', but after that the callers branch quite a bit so I'm not sure how it's connected to the control interface.
This causes a minor interface problem for arm since key presses trigger GETINFO calls but also are used to scroll the event log (ie, when the user presses 'up' at the DEBUG level it both scrolls up an entry and creates a new event, so they'll never get to the top).
This issue will partly go away when I refactor the connection panel to be independent of the main interface loop, but it still means arm and other controllers issuing periodic GETINFO calls are kinda noisy at the DEBUG level (accounting for instance triggers four GETINFO requests every ten seconds for accounting/* updates) so it would be nice if this was changed. However, if this is working as intended then I should probably filter these events out of the arm interface.
Tor version 0.2.2.13-alpha (oddly, this isn't among the version options...). Cheers! -Damian