is there like systemd service that's one-shot (run once, then exit) that can disable itself after???

[alexia@shrimp.starlightnet.work]

is there like systemd service that's one-shot (run once, then exit) that can disable itself after???

effectively, I wanna add a default wallpaper to my ublue-niri image using swww, but it seems that swww does not have a location it reads any default wallpaper from and it is exclusively configured using the swww CLI, with data then stored in $HOME/.cache/swww/{output name}

So instead my idea was to ship a small systemd service that runs swww img /usr/share/backgrounds/fedora-workstation/montclair_dark.webp once, exits, then disable itself / never run again

EDIT: Solved ​​

[elsactivitypub@goto.freakstic.fr]

@alexia yes, a user service set as `Type=oneshot` with a target for log-in

[steffo@a.junimo.party]

@alexia hmm, maybe instead of disabling itself you could use ExecCondition= to run it only if the file you want is missing?

[steffo@a.junimo.party]

@elsactivitypub @alexia doesn't that execute on each login though?

[elsactivitypub@goto.freakstic.fr]

@steffo @alexia if it's done as an enable-able service yes it would, but `systemctl start --user defaultwp` would run it once, forever

[steffo@a.junimo.party]

@elsactivitypub @alexia ah well yeah if just starting with without enabling it is a possibility then it's definitely the best solution

[alexia@shrimp.starlightnet.work]

@steffo @elsactivitypub

Sadly it isnt a possibility; BlueBuild only has enabled/disabled and masked/unmasked for system and user respectively.

[steffo@a.junimo.party]

@alexia @elsactivitypub can you have it try to turn itself off via Type=oneshot and a second ExecStart=systemctl disable yourservice ?