Opened 14 years ago

Last modified 8 years ago

#275 closed enhancement (Implemented)

setconf should be more helpful when things go wrong

Reported by: edmanm Owned by: arma
Priority: Very Low Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: edmanm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


[edmanm@adrastea:~]$ telnet localhost 9051
Connected to localhost.
Escape character is '^]'.
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]

Child Tickets

Change History (4)

comment:1 Changed 14 years ago by arma

This mostly works now. There are a few cases where we tell you that something
went wrong and go look in your logs. If any of those are particularly vague,
let me know and I can work to fix them.

Please try to break it.

comment:2 Changed 14 years ago by arma

Calling this implemented now.

comment:3 Changed 14 years ago by arma

flyspray2trac: bug closed.

comment:4 Changed 8 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.