[tor-bugs] #9860 [Tor]: junk log messages every time SETCONF changes the set of ORPorts

[Tor Bug Tracker & Wiki]

#9860: junk log messages every time SETCONF changes the set of ORPorts
-------------------------+-------------------------------------------------
     Reporter:  zwol     |      Owner:
         Type:  defect   |     Status:  needs_review
     Priority:  trivial  |  Milestone:  Tor: 0.2.4.x-final
    Component:  Tor      |    Version:  Tor: 0.2.4.17-rc
   Resolution:           |   Keywords:  tor-client tor-relay easy
Actual Points:           |  deferrable
       Points:           |  Parent ID:
-------------------------+-------------------------------------------------

Comment (by rl1987):

 If we have `log_notice()` in `retry_all_listeners()`, we are getting this
 behaviour:

 {{{
 Oct 26 16:46:48.000 [notice] New control connection opened.
 Oct 26 16:47:02.000 [notice] Opening OR listener on 0.0.0.0:9053
 Oct 26 16:47:02.000 [notice] Closing no-longer-configured OR listener on
 127.0.0.1:9090
 Oct 26 16:47:02.000 [notice] Closing no-longer-configured OR listener on
 0.0.0.0:9001
 Oct 26 16:47:09.000 [notice] Opening OR listener on 0.0.0.0:9054
 Oct 26 16:47:09.000 [notice] Closing no-longer-configured OR listener on
 0.0.0.0:9053
 Oct 26 16:47:09.000 [notice] Closing no-longer-configured OR listener on
 127.0.0.1:9090
 Oct 26 16:47:09.000 [notice] Closing no-longer-configured OR listener on
 0.0.0.0:9001
 Oct 26 16:47:25.000 [notice] Closing no-longer-configured OR listener on
 0.0.0.0:9053
 Oct 26 16:47:25.000 [notice] Closing no-longer-configured OR listener on
 127.0.0.1:9090
 Oct 26 16:47:25.000 [notice] Closing no-longer-configured OR listener on
 0.0.0.0:9001
 }}}
 Is this acceptable? Does that indicate problems with listener closing
 logic?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9860#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online