'GETINFO config-file' command on ControlPort returns the standard torrc file when it was overridden in the command line

GETINFO config-file 250-config-file=/usr/local/etc/tor/torrc

When command line begins with: --ignore-missing-torrc -f /no/file

Tor v0.2.6.6 (git-bb8c4e69ca5c8bca) running on FreeBSD with Libevent 2.0.22-stable, OpenSSL 1.0.2a and Zlib 1.2.8.

changed milestone to %Tor: unspecified

added component::core tor/tor correctness easy milestone::Tor: unspecified points::small priority::medium severity::normal status::new tor-control type::defect version::tor 0.2.6.6 labels

Actually, the log has this:

Apr 14 16:39:54.616 [notice] Configuration file "/no/file" not present, using reasonable defaults.

But why --ignore-missing-torrc didn't cause -f /no/file be ignored? So behavior is unreasonable, needs to be fixed.

Trac:
Milestone: N/A to Tor: 0.2.???
Points: N/A to small
Sponsor: N/A to N/A

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Keywords: N/A deleted, tor-03-unspecified-201612 added
Milestone: Tor: 0.3.??? to Tor: unspecified

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Severity: N/A to Normal
Keywords: N/A deleted, tor-control correctness easy added
Reviewer: N/A to N/A

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