[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #33733 [Internal Services/Tor Sysadmin Team]: How do home directories work?
#33733: How do home directories work?
-----------------------------------------------------+--------------------
Reporter: irl | Owner: tpa
Type: task | Status: new
Priority: Medium | Milestone:
Component: Internal Services/Tor Sysadmin Team | Version:
Severity: Normal | Keywords:
Actual Points: | Parent ID: #33715
Points: | Reviewer:
Sponsor: |
-----------------------------------------------------+--------------------
There seems to be little consistency here, which isn't what I expect from
an orchestrated process, so I'm maybe missing something.
Each service has a directory in /srv/{service}.torproject.org/ and then
sometimes there is a home directory, which is sometimes linked in some way
to /home/{service}. When there are multiple users for a service, they can
share the same /srv directory but then have inconsistent naming of home
directories.
Is there some documentation I can read to make sense of this?
Context: I'm putting together our Ansible roles (#33715) that should
replicate what TPA will give us when we move things to a TPA host after
we're convinced it's ready for deployment and we know what the specs will
be, but I'm having trouble generalising even from just the Onionoo and
Exit Scanner setups.
I'd like to be able to set some variables, like what usernames exist, what
groups exist, and what paths will exist and should be used for stuff, and
then let this role set that up. The service specific (e.g. Onionoo or Exit
Scanner) roles will then run equally on our AWS dev instances and the
production TPA instance.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33733>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs