Artix Linux Forum

Hi all!
Recently i encountered a problem that my system sometimes doesn't boot from first attempt due to tmpfiles-setup service failure. It boots normally, though, if i command dinit to restart boot sequence. There seems to be no logs for this service, so i don't know what exactly happens to it. I have a slight suspicion that being on aarch64+hdd while also starting some other daemons at the same time makes etmpfiles not fit to some timeouts it could have.
My question is: do we really need to run it at each boot? It seems to me that all persistent files should already be created by pacman hooks and tmpfiles-setup thus should only be limited to /run prefix

dinit 0.19.1-1
dinit-rc 0.4.8-1
etmpfiles 257.2-1

During the tmpfiles can delete your entire /home directory by design fiasco (https://github.com/systemd/systemd/issues/33349#issuecomment-2168794281) I experimented with both removing the service and removing
etmpfiles entirely with no ill effect. I was mindful however that in the latter case especially installing new or drastically changed programs might require manually intervention on my part.

A somewhat typical systemd situation of the name bearing little relation any more to what tmpfiles truely does.

Obligatory meme:
Spoiler (click to show/hide)
YMMV :)

pottering never fails to fail