Hi Keifer,
When doing Tor version upgrades (and not just config changes), there is no way to restart the process without losing uptime; as uptime records the amount of time that the Tor process has been running without interruption.
When doing version upgrades, stopping your previous version of tor and starting the new version is required, this cannot be done without interrupting the uptime. That said, uptime is not a super important stat. It is more important that you keep your tor daemon / system up to date than go for high uptime numbers.
Thanks for running relays!
On May 24, 2018, at 1:01 PM, Keifer Bly <keifer.bly@xxxxxxxxx> wrote:
“killall tor” to stop the process then “tor” to start it again usually works, but I wonder if there is a way to do this without loosing uptime as this does? Thank you.
Sent from my iPhone
On May 24, 2018, at 4:30 AM, Ralph Seichter <m16+tor@xxxxxxxxxxxxxxx> wrote:
On 24.05.18 08:17, Valter Jansons wrote:
I have not worked on macOS services, but as I understand it, executing
`sudo launchctl stop servicename && sudo launchctl stop servicename`
should do the job for restarting the service [...]
That might not work as intended, depending on macOS version and service
configuration details. Both "stop" and "start" are legacy subcommands
aimed at on-demand services and older launchd implementations.
Maybe just restarting the box is an easier method of restarting the
Tor service.
Probably.
-Ralph
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxxhttps://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays