setconf should be more helpful when things go wrong
[edmanm@adrastea:~]$ telnet localhost 9051 Trying 127.0.0.1... Connected to localhost. Escape character is '!^]'. authenticate 250 OK setconf nickname=foofoo exitpolicy=foobar orport=9030 513 Unacceptable option value
I already know that one of the arguments is unacceptable, since the response code is 513 and the control protocol spec tells me what that means. But the accompanying error message doesn't tell me which one is bogus.
This makes it hard to write useful error messages in a controller, since they all amount to saying, "Something went wrong, but I don't know what. Go look at your log, then come back and try again."
[Automatically added by flyspray2trac: Operating System: All]