Why this hack (disable a service by moving away its config) and not the more clean approach like the one take by the RPM maintainer?
..that allows one to manage (start/stop/enable/disable) each service separately using standard tools and methodologies (and not service specific ways like "if you want to disable it you have to move away its configuration file).
Simply moving away its configuration file will cause unnecessary logs since systemd will attempt to start tor.service every time:
Unable to open configuration file "/etc/tor/torrc".
[err] Reading config failed--see warnings above.
tor@default.service: control process exited, code=exited status=1
Failed to start Anonymizing overlay network for TCP.
Unit tor@default.service entered failed state.
tor@default.service start request repeated too quickly, refusing to start.
Failed to start Anonymizing overlay network for TCP.
Unit tor@default.service entered failed state.
If one monitors log for [err] log level events this isn't nice.
Also: you can not start/stop/restart tor.service separately without leaving all other tor instances untouched.
Please consider the RPM maintainer's approach, thank you!
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays