Remove unwanted systemd template instances

Artyom · 2023-07-08 20:08:36

Grepping is ongoing.
So far the only report of 'arma3server@arma3modupdate' are shell history and binary files containing line like this:

/var/lib/containers/storage/volumes/backingFsBlockDev:: 1688374732:0;sudo systemctl status arma3server@arma3modupdate.service

Which look like another sort of history.

Trilby · 2023-07-08 20:12:10

There's a good chance it would not be verbatim. The service could be activated with a variable (or command substitution) as the instance name. Rather, just the name arma3modupdate is what you should look for.

Artyom · 2023-07-09 18:38:05

It's not a bad idea.
Do you have any advice on which grep command to use to be the most accurate in the search and what is the best way to run it in the background without staying connected in SSH?

seth · 2023-07-09 18:47:46

There're several options for the latter:
https://wiki.archlinux.org/title/Allow_ … ter_logoff

Trilby wrote:

Rather, just the name arma3modupdate is what you should look for.

And again: start by searching /etc, it's the most likely location.

Artyom · 2023-07-09 19:20:12

There seem to be only two occurrences of 'arma3modupdate' in /etc

sudo grep -R arma3modupdate /etc/
/etc/systemd/system/arma3server@.service:Conflicts=arma3modupdate.service
/etc/systemd/system/multi-user.target.wants/arma3server@OpEx.service:Conflicts=arma3modupdate.service

And these refer to the dedicated update service, not the incorrect instance.
`sudo grep -R arma3modupdate /` is ongoing in a screen session.

Artyom · 2023-07-22 10:01:30

So...
After some time and a reboot, the service is still present.
What's really strange is that other instantiated services, started and shut down in the meantime, disappear after a while, just as they should.
Searching the entire file system returns almost nothing but command history.
I'm really puzzled by this, I really don't understand.

seth · 2023-07-22 20:19:12

Did you try to

systemctl mask arma3server@arma3modupdate.service

?
Of course that doesn't address the root problem at all…

Artyom · 2023-07-24 20:09:01

Unfortunately it didn't have the desired effect.
A service file is created for the instance and sent back to /dev/null but the service always comes back.
I tried to unmask it to see if creating a clean service file had solved the situation but failed.

seth · 2023-07-28 05:51:20

Last ditch broadsword spray and pray *something* suspicious shows up:

ls -lR /etc/systemd/system

Arch Linux

#26 2023-07-08 20:08:36

Re: Remove unwanted systemd template instances

#27 2023-07-08 20:12:10

Re: Remove unwanted systemd template instances

#28 2023-07-09 18:38:05

Re: Remove unwanted systemd template instances

#29 2023-07-09 18:47:46

Re: Remove unwanted systemd template instances

#30 2023-07-09 19:20:12

Re: Remove unwanted systemd template instances

#31 2023-07-22 10:01:30

Re: Remove unwanted systemd template instances

#32 2023-07-22 20:19:12

Re: Remove unwanted systemd template instances

#33 2023-07-24 20:09:01

Re: Remove unwanted systemd template instances

#34 2023-07-28 05:51:20

Re: Remove unwanted systemd template instances

Board footer