"ExitRelay 0" ignored if config files are in include directories

This

%include /etc/tor/torrc.d/

ExitRelay 0
IPv6Exit 0

seems not to work if there'S a file in /etc/tor/torrc.d/ containing

ExitRelay 1
IPv6Exit 1

changed milestone to %Tor: unspecified

added component::core tor/tor milestone::Tor: unspecified priority::medium resolution::fixed severity::normal status::closed type::defect version::tor 0.3.5.2-alpha labels

When I try this, Tor says:

Oct 06 14:16:56.061 [warn] Option 'ExitRelay' used more than once; all but the last value will be ignored.
Oct 06 14:16:56.061 [warn] Option 'IPv6Exit' used more than once; all but the last value will be ignored.

and it appears not to try to be an exit relay. Do you see that too?

If so/if not, what behavior are you seeing, and in what way does it not work?

Trac:
Status: new to needs_information
Milestone: N/A to Tor: unspecified

Trac:
Summary: "ExitRealay 0" ignored if config files are in include directories to "ExitRelay 0" ignored if config files are in include directories

Hhm, when I restart that relay, then it works as expected. When I just change the config value from 1 to 0 and reload the relay (kill -1), then the existing exit connections will stay. So maybe just a false expectation at my side about the behaviour.

We recently fixed a config include bug in #31408 (moved). Let us know if this issue happens again with a version that has the #31408 (moved) fix.

Trac:
Status: needs_information to closed
Resolution: N/A to fixed

Replying to toralf:

When I [...] reload the relay (kill -1), then the existing exit connections will stay. So maybe just a false expectation at my side about the behaviour.

Right, Tor doesn't close existing exit connections when you change your exit policy. In fact, it doesn't even close existing OR connections if you turn your ORPort to 0 (turning into just a client). The configuration options are about what you'll allow from now on, not about going through and closing all the existing conns that are not compatible ("could not have been created") with your new config.

closed

moved to tpo/core/tor#27946 (closed)