Re: [tor-relays] Help With Autoupdating Tor Software

2018-05-02 Thread Iain Learmonth
Hi, On 02/05/18 19:20, Keifer Bly wrote: > One more question, if I were to restart my relay now, would that mean that my > mid time between failures would NOT get closer to 6 days? That’s what is at > now. Assuming that you just restart it and it comes right back up again, and it's for the purp

Re: [tor-relays] Help With Autoupdating Tor Software

2018-05-02 Thread Keifer Bly
One more question, if I were to restart my relay now, would that mean that my mid time between failures would NOT get closer to 6 days? That’s what is at now. Thanks. Sent from my iPhone > On May 2, 2018, at 2:33 AM, teor wrote: > > >>> On 2 May 2018, at 19:20, Iain Learmonth wrote: >>> >>

Re: [tor-relays] Help With Autoupdating Tor Software

2018-05-02 Thread teor
> On 2 May 2018, at 19:20, Iain Learmonth wrote: > >> On 02/05/18 09:50, teor wrote: >> Being in the consensus is called "Running", but what it actually means is >> that a majority of directory authorities found your relay reachable. >> >> So perhaps we could use: >> * uptime for the amount of

Re: [tor-relays] Help With Autoupdating Tor Software

2018-05-02 Thread Iain Learmonth
Hi, On 02/05/18 09:50, teor wrote: > Being in the consensus is called "Running", but what it actually means is > that a majority of directory authorities found your relay reachable. > > So perhaps we could use: > * uptime for the amount of time since the tor process started > * reachable time for

Re: [tor-relays] Help With Autoupdating Tor Software

2018-05-02 Thread teor
> On 2 May 2018, at 18:32, Iain Learmonth wrote: > >> On 02/05/18 02:09, Keifer Bly wrote: >> My suspicion is that my posted uptime was retained because I did not >> restart the relay software while my router firmware was updating (it was >> offline for about 2 hours), but it thought I’d share t

Re: [tor-relays] Help With Autoupdating Tor Software

2018-05-02 Thread Iain Learmonth
Hi, On 02/05/18 02:09, Keifer Bly wrote: > My suspicion is that my posted uptime was retained because I did not > restart the relay software while my router firmware was updating (it was > offline for about 2 hours), but it thought I’d share this little thing I > noticed. You're correct. The upti

Re: [tor-relays] Help With Autoupdating Tor Software

2018-05-01 Thread Keifer Bly
3:44 PM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Help With Autoupdating Tor Software > On 2 May 2018, at 03:58, Keifer Bly wrote: > > do shell script "$ which brew > /usr/local/bin/brew update" > do shell script "$ which brew > /usr/

Re: [tor-relays] Help With Autoupdating Tor Software

2018-05-01 Thread teor
> On 2 May 2018, at 03:58, Keifer Bly wrote: > > do shell script "$ which brew > /usr/local/bin/brew update" > do shell script "$ which brew > /usr/local/bin/brew upgrade tor" > end > > > When the script is run, the output is this: $ which brew > sh: $: command not found /usr/local/bin/bre

Re: [tor-relays] Help With Autoupdating Tor Software

2018-05-01 Thread Spiros Andreou
Hi Keifer, Depending on the version of OS X you’re using (hopefully it’s a recent one), you might have more reliable script execution using Launchd rather than Cron. For your script, I would stick to bash as you seem to be combining AppleScript and shell script. Make the following text file: #

[tor-relays] Help With Autoupdating Tor Software

2018-05-01 Thread Keifer Bly
Hello, So on Mac OS X, I am using crontab to automatically run a script I wrote for Mac OS High Sierra to automatically update the tor relaying software every day at 1am. The cron command I am using is this: 0 1 * * * /Users/oldimac/Desktop/update\ tor.scpt The script I wrote seems to work fi