[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[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:
-------------------------+--------------------------------------------------
Hi, to try and improve arm's performance I've introduced client side
caching for relatively static configuration parameters. However, I've run
into an issue for the case where other controllers tamper these values
(for instance, changing options in vidalia while arm's running).
Currently there's no notifications for SETCONF calls. In particular,
control_setconf_helper (or/control.c line 623) doesn't log anything except
warnings in case of failure. Could successful calls be made to produce an
event, perhaps at the INFO level? Thanks! -Damian
PS. I'm suspecting that for heavily loaded relays having tor provide all
INFO level events just on the off chance that this'll occur is gonna cause
a pretty big hit in terms of performance. If it's a problem I'll probably
just listen to them if the load's low (not a good solution, but the cure
is probably worse than the disease in that case).
I'd much rather avoid drinking from the fire hose just to pick up this
piece of information. While the INFO and DEBUG levels have a lot of nice
information controllers can use to infer things for which no GETINFO
option exists, this seems likely to come at a very high price.
Do we have any metrics for the performance costs of listening to these
events? If problematic, any thoughts on how this might be addressed? One
option would be letting controllers provide regex filters for the events
they'd like to receive.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1692>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online