no shutdown descriptor published when ORPort is closed but client stays up
(Posted by request from Scott Bennett.)
Category: tor router -> tor client
Operating System: observed on FreeBSD 7.2-STABLE
Reported Version: 0.2.2.3-alpha
Title: no shutdown descriptor published when ORPort is closed but client stays up
Reported By: Scott Bennett
Description: When tor is running as both a router and a client, if a SIGINT
is sent to tor, tor closes the ORPort (and DirPort if applicable),
publishes a shutdown descriptor (i.e., a new descriptor in which the
"observed maximum 10s data rate in previous 24 hrs" is set to 0 to
discourage further attempts to include the node in new circuits), and
proceeds with the rest of the shutdown procedure. However, given the
same starting conditions, if the ORPort line in torrc is commented out
and a SIGHUP is sent to tor, tor will read the updated torrc, notice
that the ORPort is no longer to be used, close the ORPort (and DirPort
if applicable), and continue operation as a client process without
publishing a shutdown procedure. This situation results in many
unnecessary attempts by clients and routers to connect to the ORPort
(and DirPort if applicable) after it has been closed, wasting time and
causing avoidable circuit construction failures. This was observed in
tor 0.2.2.3-alpha. I haven't yet tried it in 0.2.2.5-alpha.
[Automatically added by flyspray2trac: Operating System: BSD]