888
systemdeez nuts (sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
[-] snake_case_lover@lemmy.world 12 points 8 months ago

it doesn't run a job it waits for your jobs to end. You can set the default want time. Its the same thing on windows that asks programs to close before shutting down. If a critical application got stuck systemd has nothing to do with it

[-] Deckweiss@lemmy.world 3 points 8 months ago* (last edited 8 months ago)

I know what it is. But it literally says "A stop job is running" and since english is not my first language, I had no good idea how to better express the technicalities of it in a short sentence.

As for it having nothing to do with systemd:

I am dual booting arch and artix, because I am currently in the middle of transitioning. I have the exact same packages on both installs (+ some extra openrc packages on artix).

  • About 30% of the shutdowns on arch do the stop job thing. It happens randomly without any changes being done by me between the sessions.

  • 0% of the shutdowns on artix take more than 5 seconds.

I know that I can configure it. But why is 90 seconds a default? It is utterly unreasonable. You cite windows doing it, but compare it instead to mac, which has extremely fast powerups and shutdowns.

And back to the technicalities, openrc doesn't say "a stop job is running", so who runs the stop job if not systemd?

[-] MartianSands@sh.itjust.works 8 points 8 months ago

The question you should be asking is what's wrong with that job which is causing it to run for long enough that the timeout has to kill it.

Systemd isn't the problem here, all it's doing is making it easy to find out what process is slowing down your shutdown, and making sure it doesn't stall forever

this post was submitted on 19 Apr 2024
888 points (98.7% liked)

linuxmemes

21282 readers
560 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 members of the community for any reason.
  • 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.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 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. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    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 fork-bomb your computer.

    founded 2 years ago
    MODERATORS