Creating a bug report/issue
- DietPi version |
- Distro version |
- Kernel version |
Linux DietPi 5.15.32-v7+ #1538 SMP Thu Mar 31 19:38:48 BST 2022 armv7l GNU/Linux
- SBC model |
RPi 2 Model B (armv7l)
- Power supply used | (EG: 5V 1A RAVpower)
- SD card used | (EG: SanDisk ultra)
Additional Information (if applicable)
- Software title | (TOR relay)
Steps to reproduce
- …Install TOR relay from dietpi-software
- …Try to disable TOR with “sudo systemctl disable tor.service and sudo systemctl disable firstname.lastname@example.org”
- …Reboot and see that TOR starts
- …Make all steps of startup - How to prevent Tor from starting automatically on Ubuntu server? - Ask Ubuntu
- …TOR starts after reboot again.
I don’t know much about linux, so i’m missing something or doing wrong? (Unbound or Pihole let me disabling it problemless with “sudo systemctl disable unbound/pihole”)
- …TOR relay should not autostart
Welcome to our community.
This is an exspected behaviour as DietPi has taken control on the service. You would need to disable DietPi control, to be able to manage the service manually. You can do this using
dietpi-services. Select your service and set it to
[Systemd controlled] +
[excluded], like this
●─ Service Control ──────────────────────────────●
State : [active]
Mode : [Systemd controlled]
Include/Exclude : [excluded]
Status : Display systemd status log
Wow, that is so simple (after you know where to look).
You can leave it at
DietPi controlled btw, so systemd doesn’t start it either:
systemd controlled equals
systemctl enable, so that systemd is effectively starting it at boot.
DietPi controlled equals
systemctl disable so that DietPi is effectively starting it at boot, at a later stage in defined order.
Excluded tells DietPi to not start it either.