Source is currently the bottom most answer - https://unix.stackexchange.com/questions/225401/how-to-see-full-log-from-systemctl-status-service
- Why not just use journalctl directly at that point - That’s what this answer actually suggests, but apparently typing “journalctl” is tedious, so let’s instead break everything for no good reason and blame systemd. - Do aliases break autocompletion? If not, that’s the solution 
- Why make things up? Why lie? Not a single person argued that typing journalctl was too tedious, let alone OP. - You should check the source OP posted before making an ass of yourself. - I did, and even rechecked it just now- not a single person says using journalctl is tedious. A few say it doesn’t give them the data they actually are needing, but nobody is randomly hating on journalctl. 
- I just checked too, ain’t nobody saying it’s too tedious 
- Yeah me too. I checked SO and couldn’t find it. 
 
 
 
 
- The joke is that at Microsoft, this kind of fix is the upstream. 
- Ah, just like the good old days. I remember many a weekend spent trying to fix one issue on my rig only for 6 others to pop up, and then 12 more after like some crazy linux mandelbrot. 
- I don’t get it - Why are we beating a dead horse 







