Mar 06 11:13:48 JJK-Laptop0 systemd: Started TeamViewer remote control daemon. Mar 06 11:13:48 JJK-Laptop0 systemd: rvice: Can't open PID file /var/run/teamviewerd.pid (yet?) after> Mar 06 11:13:48 JJK-Laptop0 systemd: Starting TeamViewer remote control daemon. └─11430 /opt/teamviewer/tv_bin/teamviewerd -d Process: 11428 ExecStart=/opt/teamviewer/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)ĬGroup: /system.slice/rvice Loaded: loaded (/usr/lib/systemd/system/rvice disabled vendor preset: disabled)Īctive: active (running) since Tue 11:13:48 CET 2s ago rvice - TeamViewer remote control daemon.Output after systemctl start teamviewerd: Network process already started (or error)Īfter this, I cannot find the process running using ps -aux I think that's a good idea, but it should probably come with some explanation comments. I can show you what to clean up to fully remove the package. If you are going to advise your package's users to delete it, at least add a warning that it may have significant consequences. It will affect much more than just TeamViewer. You should definitely not be deleting a systemd file just because TeamViewer happens to read it. Google TeamViewer Linux 'machine-id' to see what it has to do with TeamViewer. Tmpfiles.d allows declaring a list of files and directories created by programs at runtime, including log directories, if that's what you're looking for. The only exception are configuration files, as indicated by the backup=(.) array in PKGBUILD files, and when pacman -R is invoked also with -n.

Uninstalling and reinstalling a package should have no net effect on the system.

I don't think packages should do anything of the sort, unless the files are created during installation.

I can delete anything that Teamviewer creates in system folders.

Teamviewer 13 linux