• HM King Charles III DG FD@feddit.ukEnglish
    7·
    1 hour ago

    Everyone arguing about the amount of keypresses to type a shutdown command and time it takes to shutdown… I just power it off at the wall. One button press, shutdown is near instantaneous

    • Kairos@lemmy.today
      8·
      2 hours ago

      (X time / 1:30) but the second time will be extended indefinitely for some fucking reason.

    • anon5621@lemmy.ml
      4·
      2 hours ago

      Yes but no, u can in config file of systemd change timeout to 5,10 second or other number of seconds which u wish before it will kill it

    • RustyNova@lemmy.world
      3·
      1 hour ago

      My always plugged in HDD with bees on it does that. 1 minute to shutdown at least because there’s always some kind of extend read or dedupe that need a sync.

      … I brought this upon myself so I don’t have to complain.

      • realitaetsverlust@piefed.zipEnglish
        1·
        39 minutes ago

        I think that depends on the setting, I had situations where one of my docker containers took ages to shutdown and it would just say 00/02 00s but when it reached that limit, it would just go up.

        • TwilightKiddy@scribe.disroot.orgEnglish
          1·
          14 minutes ago

          Individual services can override the default 90 seconds timeout. But then you can override their override if you think you are smarter, of course.

      • Thorry@feddit.org
        8·
        2 hours ago

        Well you say that, but I’ve seen the countdown go past and then reset to a higher number often.

        • TwilightKiddy@scribe.disroot.orgEnglish
          1·
          13 minutes ago

          I entrust you with this horror, go figure out what to blame.

          shutdown-analyze.sh 
          #! /usr/bin/env bash
shutdown_start=$(journalctl -b -1 -u systemd-logind --grep="System is (powering down|rebooting)" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP)
shutdown_start=$((shutdown_start / 1000000))
units=$(journalctl -b -1 --since=@$shutdown_start --output=cat --no-pager --output-fields=UNIT JOB_TYPE=stop CODE_FUNC=job_emit_start_message)

for u in $units; do
    stopping_start=$(journalctl -b -1 --since=@$shutdown_start -u "$u" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP JOB_TYPE=stop CODE_FUNC=job_emit_start_message _SYSTEMD_UNIT=init.scope)
    stopping_end=$(journalctl -b -1 --since=@$shutdown_start -u "$u" --output=cat --no-pager --output-fields=_SOURCE_REALTIME_TIMESTAMP JOB_TYPE=stop CODE_FUNC=job_emit_done_message _SYSTEMD_UNIT=init.scope)
    duration_human=$(systemd-analyze timespan $((stopping_end - stopping_start))us | tail -1 | sed 's/.*: //')
    printf "%s\t%10s %s\n" $((stopping_end - stopping_start)) "$duration_human" "$u"
done | sort -rn | cut -f 2
  • tuckerm@feddit.onlineEnglish
    3·
    1 hour ago

    People give Windows a lot of flak for this, but at least it usually does turn off after finishing its updates.

    MacOS is the one that will just literally ignore the fact that you told it to shut down. Or it takes forever to tell you that a program has unsaved changes. At least Windows will tell you that right away, so that you see the “something is preventing shutdown” message before you walk away from the computer. Your Mac will wait 15 minutes, and then be like, “by the way, the browser doesn’t want to close.”

    • drcobaltjedi@programming.dev
      1·
      6 minutes ago

      “Update and Shutdown” still acts as “Update and Restart” on windows. They added a whole new feature that is indistinguishable from the previous feature.

      Though I agree macos has the problem of “well Firefox was open so I was stuck here over night”

  • Rhaedas@fedia.io
    111·
    3 hours ago

    Five seconds? What’s hogging that system? Mine is about two, at most, from the WM shutdown selection.

  • pelya@lemmy.world
    6·
    2 hours ago

    Just poweroff is fine. Why lose extra 2.5 seconds typing two words when one word will suffice?