Opened 11 years ago

Last modified 7 years ago

#684 closed enhancement (Won't implement)

Recover from Config Parse Errors on HUP

Reported by: BarkerJr Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.2.0.25-rc
Severity: Keywords:
Cc: BarkerJr, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Currently, if there's an error in the config, sending HUP to tor will cause it to exit. It should, instead, revert back to its previous configuration.

[Automatically added by flyspray2trac: Operating System: Other Linux]

Child Tickets

Change History (4)

comment:1 Changed 11 years ago by nickm

We considered this behavior before and decided not to implement it, mainly because we didn't want people to believe
they had made important config changes to their Tors when in fact those changes had not gone through.

A better solution might be a mini-controller script that tries to load the new configuration, and reports success or
failure.

comment:2 Changed 11 years ago by arma

There's a way to check whether or not your new config will parse and work:

tor --verify-config

The debian package now tries that first and doesn't attempt a hup if
verify-config returns a failure.

Other packages ought to use this approach too.

Going to mark this one as 'won't implement'.

comment:3 Changed 11 years ago by arma

flyspray2trac: bug closed.

comment:4 Changed 7 years ago by nickm

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