Every time when i poweron the pc, some proccess are started with the system. Some of them are Anydesk and SQL.
I had disable sql from start alongside the system with systemctl disable mysql, so i think that i need to do the same with anydesk.
But why these programs make this? Even if i dont start the app/program, they will be there, eating resources from the start… WHY THIS HAPPEN!!!
Edit: Something i forgot to put: why they have root permissions? this happen no wonder the system i install these programms, they have the same behaviour


Wonderful day!
May I ask how did you install these programs?
For example, AnyDesk. The underlying service might be installed from the official repository DEB package.
As we may see, in the following package:
- https://deb.anydesk.com/pool/main/a/anydesk/anydesk_8.0.4_amd64.deb
There’s a standard “postinst” script inside that installs the service:
"postinst" preview
#!/bin/bash set -e command_exists() { command -v "$1" > /dev/null 2>&1 } if [ "$1" = configure ]; then INITSYS=$(ls -al /proc/1/exe | awk -F' ' '{print $NF}' | awk -F'/' '{print $NF}') if [ "systemd" == "$INITSYS" ]; then if [ -e /etc/systemd/system/anydesk.service ]; then rm /etc/systemd/system/anydesk.service fi cp /usr/share/anydesk/files/systemd/anydesk.service /etc/systemd/system/anydesk.service systemctl daemon-reload deb-systemd-invoke enable anydesk deb-systemd-invoke start anydesk elif [ "init" == "$INITSYS" ]; then if [ -e /etc/init.d/anydesk ]; then rm /etc/init.d/anydesk fi chmod +x /usr/share/anydesk/files/init/anydesk ln -s /usr/share/anydesk/files/init/anydesk /etc/init.d/anydesk update-rc.d anydesk defaults invoke-rc.d anydesk start fi command_exists update-menus && update-menus command_exists update-desktop-database && update-desktop-database command_exists xdg-desktop-menu && xdg-desktop-menu forceupdate fiSince the script is copied into “system” path (not the User’s “/etc/systemd/user/*”), it is executed by “root” by default, unless specifically specified in the service itself (e.g., directive “User=”).
Just in case, “enabling” in marvelous Systemd is merely a symlink added to the directory the OS probes on boot. You should see the symlink location on service '(dis-)enabling".