[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-dev] documenting reload vs. restart requirements per torrc option



Hi,

I like unbound's documentation with this regards, for example they say
in their man page:

> The  interfaces  are not changed on a reload (kill -HUP)
>              but only on restart.


Could we add such information to every torrc option in the manual?


background: 

In relayor I need to reload/restart tor daemons on configuration changes
currently I blindly assume reload is fine, because in most cases it is
but it comes with the prices of accepting a certain level of error
since not all configuration changes can be applied by reloads.
To fix this I'd need to have authoritative information about
what changes require restarts vs. reloads.



[1] https://unbound.net/documentation/unbound.conf.html

-- 
https://twitter.com/nusenu_
https://mastodon.social/@nusenu

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev