After installing a tor relay with newest expert package Tor-0.2.2.9-alpha-i386-Bundle I wondered why tor is running as $USER, but not as tor.
I new user _tor is created and the group daemon exists as well.
A quick look at the script addsysuser gives a hint:
At least the lines 58 & 69 …
hmm, looking at the list of relays, MacOS X relays are seldom, even concerning the rate of MacOS X in general. But most MacOS X machines aren't real servers and the users are normal users. For them installing a Tor relay is difficult to handle, the torrc is heavy stuff, since words like socks, port etc. are far beyond their scope. But even on these machines it could be useful to run a Tor relay, at least during daytime.
Anyhow I can be wrong but the install scripts are still from 2007 and it looks as if they need some refreshments.
1.) MacOS X has moved to launchd. Therefor we need a LaunchDaemon xml-file in /Library/LaunchDaemons which should in bash script as here document look alike:
Trac: Status: new to accepted Keywords: N/Adeleted, N/Aadded Milestone: N/Ato Tor: 0.2.2.x-final Owner: N/Ato phobos Description: After installing a tor relay with newest expert package Tor-0.2.2.9-alpha-i386-Bundle I wondered why tor is running as $USER, but not as tor.
I new user _tor is created and the group daemon exists as well.
A quick look at the script addsysuser gives a hint:
At least the lines 58 & 69 …
…can’t work properly (besides others) with Snowleopard since nituil and nidump doesn't exist anymore. As far as I know there are substituted by dscl.
[Automatically added by flyspray2trac: Operating System: OSX 10.6 Snow Leopard]
to
After installing a tor relay with newest expert package Tor-0.2.2.9-alpha-i386-Bundle I wondered why tor is running as $USER, but not as tor.
I new user _tor is created and the group daemon exists as well.
A quick look at the script addsysuser gives a hint:
At least the lines 58 & 69 …
Unfortunately, i think the answer is to run the vidalia bundle. OS X requires a gui anyway. If you want to run a tor relay from cli, you could also compile the source yourself.
I'll try to hack out a dscl vs. nidump/niutil fix into the expert installer. I'd rather just dump the mac installer and go with drag and drop altogether.
Doing triage: it looks like this might be a new bug to 0.2.2.x, so maybe we'll want to try to resolve it during the lifetime of 0.2.2. The best fix might be to drop support for expert bundles for osx altogether.
It shouldn't block the release candidate in any case.
I still think we should drop them. Branch remove-osx-expert-package in my repo removes everything from tor.git that still references the package. Erinn you should make sure that you have everything that gets removed here saved somewhere to put it into your build instructions repository (and we should indeed first make sure everything is already committed and pushed before we remove it here).