No.230
So, yesterday I was rebooting my laptop and noticed a message during the systemd boot sequence that said something along the lines of "A start job is running for Creating volatile files and directories".
Of course, this weirded me out because I have the boot sequence set to silent and nothing like this ever happened. Searching around I discovered it should be a legit part of systemd (part of tmpfiles.d), and there is an entry in my systemctl that is listed as Creating volatile files and directories which call systemd-tmpfiles-setup.service. I guess it's just a part of systemd, but I am still afraid of what could it be because this shit never happened before. All I did in my last session was installing and uninstalling a few games (non-root, of course) and reconfiguring my locales (root, but I haven't been able to reproduce the error by doing it again so I guess it is not because of this).
So, does anyone have any idea of why did this happen? I got very surprised because quiet mode just prints a few strings on screen and then boots directly to the login console, and somehow this managed to get on screen and made boot at least 40-50s longer. Rebooting again after that returned the boot sequence to its default state, but sadly I just discovered my journal was configured to log the last boot.
rkhunter and chkrootkit showed nothing. Should I be afraid of this behaviour or is it perfectly normal?
tl;dr "A start job is running for Creating volatile files and directories" pops up during a quiet boot, freak out, things have apparently returned to normal, still paranoid.
No.235
It wouldn't have felt like home without a paranoid systemd thread or two. Thank you, anon.
No.236
>>235The main difference is I am implying it very subtly instead of listing all systemd flaws.
I also think it could be the result of some crazy exploit in case it is not normal.