tor process cannot process SIGHUP when a relative path to a config file is given
Run tor with a relative path to a config file, e.g.
./tor -f ../etc/tor/torrc
Issue a SIGHUP to it. It fails with:
Oct 12 21:37:35.000 [notice] Received reload signal (hup). Reloading config and resetting internal state. Oct 12 21:37:35.000 [warn] Unable to open configuration file "/[obfuscated]/tor-network/dirauth1/var/lib/tor/../etc/tor/torrc.dirauth". Oct 12 21:37:35.000 [err] Reading config failed--see warnings above. For usage, try -h. Oct 12 21:37:35.000 [warn] Restart failed (config error?). Exiting.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information