this post was submitted on 06 May 2025
107 points (98.2% liked)

linuxmemes

25111 readers
952 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    • Β 

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    107
    "Do this simple hack to make this command usable, then another hack to fix the problem your hack does" (programming.dev)
    submitted 3 weeks ago by ICastFist to c/[email protected]
    11 comments fedilink hide all child comments
     

    Source is currently the bottom most answer - https://unix.stackexchange.com/questions/225401/how-to-see-full-log-from-systemctl-status-service

    top 11 comments
    sorted by: hot top controversial new old
    [–] [email protected] 32 points 3 weeks ago (1 children)

    Why not just use journalctl directly at that point

    [–] [email protected] 28 points 3 weeks ago (2 children)

    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.

    [–] [email protected] 13 points 3 weeks ago

    Do aliases break autocompletion? If not, that's the solution

    [–] [email protected] 1 points 3 weeks ago (1 children)

    Why make things up? Why lie? Not a single person argued that typing journalctl was too tedious, let alone OP.

    [–] [email protected] 6 points 3 weeks ago (3 children)

    You should check the source OP posted before making an ass of yourself.

    [–] [email protected] 2 points 3 weeks ago

    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.

    [–] [email protected] 1 points 3 weeks ago

    I just checked too, ain't nobody saying it's too tedious

    [–] [email protected] 1 points 3 weeks ago

    Yeah me too. I checked SO and couldn't find it.

    [–] [email protected] 20 points 3 weeks ago

    The joke is that at Microsoft, this kind of fix is the upstream.

    [–] [email protected] 12 points 3 weeks ago* (last edited 3 weeks ago)

    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.

    [–] [email protected] 2 points 2 weeks ago

    I don't get it

    Why are we beating a dead horse