this post was submitted on 05 Jun 2026
767 points (98.1% liked)

linuxmemes

31675 readers
1667 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.
  • Don't come looking for advice, this is not the right community.
    • 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 3 years ago
    MODERATORS
    zephyr@lemmy.world
    rtxn@lemmy.world
    767
    bye bye processes, you go sleep now :))) (lemmy.dbzer0.com)
    submitted 4 days ago* (last edited 4 days ago) by empireOfLove2@lemmy.dbzer0.com to c/linuxmemes@lemmy.world
    130 comments fedilink hide all child comments
     

    reupload because i mixed up sigterm and sigkill like a dumb fuck

    you are viewing a single comment's thread
    view the rest of the comments
    [–] de_lancre@lemmy.world 21 points 3 days ago (2 children)

    I don't know what comment section or post are talking about. Default timer for systemd on arch is 3 minutes (and I think it's default for most distros). Whenever some service fails to quit on reboot, system will stuck for 3 minutes until systemd decide to kill it. I need to manually configure it lower to like, 10 seconds, cause there shit ton of services that always fails to quit.

    And not like I'm using old pentium - my system build on AM5 with amd 7700x, 128gb of 5600MT\s ram and 7900xtx, with kingston nvme pcie4 ssd's on top of that. It's literally "best case scenario".

    [–] sem@piefed.blahaj.zone 2 points 3 days ago

    I guess the difference is that sigterm usually closes all the programs pretty quickly; but ITT I am learning that is not always the case!

    [–] DaforLynx@lemmy.zip 1 points 3 days ago (1 children)

    How do you configure this? I have often encountered minute-long restarts most of which was fixed by adding a service to kill the wine server on shutdown, but still it sometimes happens.

    [–] de_lancre@lemmy.world 2 points 2 days ago (1 children)

    How do you configure this?

    Idealistically - you supposed to figure out what wrong with particular service that causing long shutdowns, by using: journalctl -b -1 -e or something like that. You can also use systemd-analyze blame to do the opposite and figure out what causing long startup.

    But if you a normal human being that doesn't have weeks to figure out bugs on kernel level with AMDGPU power management, then there a simpler solution - you just need to lower timer. In file:

    /etc/systemd/system.conf

    Uncomment (remove #) this line and set it either in minutes or seconds:

    DefaultTimeoutStopSec=10s

    I really don't understand why default is so high. Even on old and weak hardware shut down shouldn't take too much time.

    [–] DaforLynx@lemmy.zip 2 points 2 days ago

    Thank you so much! Hopefully this works.