If that approach is enough then tail -f /var/log/*
could work too with multiple files, it'll "follow" all the files and display only new lines.

ferk@lemmy.ml
Posts
-
systemd has been a complete, utter, unmitigated success -
systemd has been a complete, utter, unmitigated successI feel that generally, when the issue is that the person is an arse, then the complaints are often not about the software. You might see people campaigning to boicot the software out of spite, but they won't give you a technical reason, other than them not wanting the creator to get any credit for it.
When the complaints are about discrepancies in the way the software is designed (like it was with systemd), there's no reason to expect the person to be an arse. Though him not being an arse does not make the criticism about his software invalid... in the same way as him being an arse would not have made the software technically worthless. Don't fall for the ad-hominem.
-
systemd has been a complete, utter, unmitigated successI don't know why they are downvoting you, it's true. I'm dealing with this kind of problem currently.. sometimes the boot lasts forever to the point that I have to use AltGr+SysRq commands to force kill everything.. other times it simply boots as normal. It's not consistent at all.
At least before with the old init it was relatively simple to dig into the scripts and make changes to them.. I feel now with systemd it's a lot more opaque and harder to deal with. I wouldn't even know how to approach the problem,
systemd-analyze blame
does not help, since the times I actually get to boot look normal. But I do believe it must have to do with the mountpoints because often they are what takes the longest.
Any advice on what should I do would be welcome.Also, I have a separate Bazzite install in my living room TV, and while that one does not get locked, sometimes NetworkManager simply is not running after boot... I got fed up to the point that I wrote a workaround by creating a rc.local script to have it run, so I can have it available reliably when the system starts (that fixed it.. though some cifs mountpoints often do not get mounted.. so I'm considering adding the mount command to the same rc.local script too....).