#31693 closed defect (fixed)

Have GetTor start automatically when machine reboots

Reported by: phw Owned by:
Priority: Very High Milestone:
Component: Applications/GetTor Version:
Severity: Critical Keywords:
Cc: hiro, traumschule, gaba, phw Actual Points:
Parent ID: Points: 0.1
Reviewer: Sponsor:

Description (last modified by phw)

Getulum last rebooted on 2019-09-07 at 20:02:55 UTC. After the machine came back online, GetTor didn't start again and it has been offline for the last three days. We really need systemd (or whatever) to start the service automatically. Let's set this up as a user-level service as described here: https://help.torproject.org/tsa/doc/services/

Here's a possible gettor.service file:

Description=GetTor distributes links to Tor Browser over email.

ExecStart=/bin/sh -c 'cd /home/gettor/bin/ && source venv/bin/activate && bin/gettor_service start'


I believe that we still need a sysadmin to run loginctl enable-linger gettor to enable lingering services for the gettor user: see the section "sysadmin stuff" in https://help.torproject.org/tsa/doc/services/

Child Tickets

Change History (2)

comment:1 Changed 14 months ago by phw

Description: modified (diff)

comment:2 Changed 14 months ago by anarcat

Resolution: fixed
Status: newclosed

done, through puppet. systemd --user is now running for user gettor on getulum:

           │ └─user-1536.slice
           │   └─user@1536.service
           │     └─init.scope
           │       ├─10304 /lib/systemd/systemd --user
           │       └─10305 (sd-pam)
Note: See TracTickets for help on using tickets.