top 50 comments

sorted by: hot top controversial new old
[–] [S] 67 points 4 days ago (1 child)

Reminds me of one of the truest comics I ever read.

collapsed inline mediaDsmoxSmOInIZlnj.jpg

  • source
  • hideshow 2 child comments
  • [–] [S] 5 points 3 days ago (3 children)

    It is weird isn't it.

    Why do they make it so bad?

    I imagine half of linux users could make better automated update rules in their cron.

    So many better ways.

    So why are they making it intentionally bad?

    ... Sabotage from Microsoft employees who hate Microsoft?

    ... Part of a larger Embrace Extent Extinguish tactic, where they've already embraced the Linux Foundation etc enough, they're ready to extinguish Windows, already having sufficient monopolistic total-control hooks in Linux???

    What are they up to? There has to be a reason it's so bad. There has to be a reason they go out of their way to make it so bad.

    It surely can't just be the effects of The Corporation, the hierarchies and compartmentalisations and bureaucracy of the structure where they don't understand (or even perhaps do understand [and maybe have seen Kevlin Henney's excellent talk on clean code vs enterprise programming] but) can't do anything about it, can it?

    What are they building in there? We don't get to see, we don't get to know, just trust them, they know best when and how, and so you are not allowed to change it.

    We are not doing that any more.

  • source
  • parent
  • hideshow 3 child comments
  • load more comments (3 replies)
  • [–] [S] 56 points 3 days ago (2 children)

    [**    ] A stop job is running for Session c1 of User gdm (49s / 1min 30s)

  • source
  • hideshow 3 child comments
  • load more comments (1 reply)
    [–] [S] 108 points 4 days ago (7 children)
  • [–] [S] 43 points 4 days ago (2 children)

    At least it tells you how long it'll take before it decides to SIGKILL whatever is holding the shutdown sequence.

  • source
  • parent
  • hideshow 4 child comments
  • [–] [S] 18 points 4 days ago (2 children)

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

  • source
  • parent
  • hideshow 3 child comments
  • [–] [S] 13 points 4 days ago* (last edited 4 days ago) (2 children)

    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
    

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (2 replies)
  • load more comments (1 reply)
  • [–] [S] 9 points 4 days ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 6 points 4 days 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.

  • source
  • parent
  • load more comments (2 replies)
    [–] [S] 33 points 4 days ago (2 children)

    Windows cannot shut down because there is a folder open.

  • source
  • hideshow 2 child comments
  • load more comments (2 replies)
    [–] [S] 18 points 4 days ago (4 children)

    I've never used systemd to shut down

    Sudo shutdown -h now works on the Mac

  • source
  • hideshow 6 child comments
  • load more comments (2 replies)
    [–] [S] 14 points 4 days ago (9 children)

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

  • source
  • hideshow 10 child comments
  • load more comments (8 replies)
    [–] [S] 13 points 3 days ago (2 children)

    It's even worse, when I tell my work Windows 11 computer to shut down and I have to choose update and shutdown because it decided to do updates, sometimes it reboots a few times but then it doesn't turn off afterwards.

    I'm never going to install Windows 11 on any of my devices, it's so bad.

  • source
  • hideshow 4 child comments
  • [–] [S] 12 points 3 days ago (1 child)

    I bought a new mini PC the other day that shipped with windows 11. Before installing Linux I thought "I'll just boot into windows to make sure the hardware is all correct".

    I got as far as the windows welcome screen and thought "it's actually just going to be faster and easier to install Debian instead of going through all this windows bullshit"

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 9 points 3 days ago

    I got a new Mini a month ago. Before I even powered it up, I stabbed a USB stick into it, hit escape on boot, and killed that bitch with Kinonite.

    There are two things a person needs to do when starting up a fresh new computer: First, you must bathe in the purifying waters of Lake Minnetonka, and never, ever let Windows have even a single chance to live.

  • source
  • parent
  • [–] [S] 8 points 3 days ago (2 children)

    Or my old windows 10 machine would wake itself up in the middle of the night to run updates that the group policy wouldn't even allow it to download without my permission and then just sit there. If I hadn't fallen asleep yet, I'd notice the monitor light up the next room and get up swearing at Microsoft until I tracked down where the wakeup timer was set and disabled it. Only to find it re-enabled after some updates.

    Fuck Microsoft.

  • source
  • parent
  • hideshow 3 child comments
  • load more comments (1 reply)
  • [–] [S] 13 points 3 days ago (2 children)
    load more comments (2 replies)
    [–] [S] 11 points 3 days ago

    systemctl invariably hangs on waitimg for some job to finish. systemd-shutdown-inhibitor is hideous.

    poweroff -ff

  • source
  • [–] [S] 10 points 4 days ago (4 children)

    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

  • source
  • hideshow 4 child comments
  • load more comments (4 replies)
    [–] [S] 8 points 2 days ago*

    Powers on

    Immediately starts shut down

    Refuses to close because the following programs are still running

    The list is empty

  • source
  • [–] [S] 8 points 3 days ago (6 children)

    Are you guys really using a command to shut down a computer?

    Because you can do the same with Windows, but nobody uses it because it is just not convenient to use commands for that.

    shutdown /s

  • source
  • hideshow 7 child comments
  • load more comments (5 replies)
    [–] [S] 8 points 3 days ago (3 children)

    You can just type "shutdown now" and it does.

  • source
  • hideshow 3 child comments
  • load more comments (3 replies)
    [–] [S] 7 points 3 days ago (1 child)

    it's now safe to turn off your computer

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] [S] 7 points 3 days ago (2 children)

    Not to be that guy but...

    shutdown /s /f /t 0

  • source
  • hideshow 2 child comments
  • load more comments (2 replies)
    [–] [S] 12 points 4 days ago

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

  • source
  • [–] [S] 6 points 4 days ago (1 child)

    Apparently there are a lot of ways to shutdown. halt is my preference from the command line.

  • source
  • hideshow 2 child comments
  • [–] [S] 5 points 3 days ago (4 children)

    I was always particularly fond of windows turning my laptop on, running updates, and then going into hibernation, which then caused a blue screen trying to come out of it.

    The laptop had sleep and hibernation disabled, all of the wake-on-events and automatic updates were disabled as well. (It was an older cranky thing and deserved rest - or to be taken out back and shot.)

    Yet, somehow it always turned on for update day, even after I blocked it from the internet via the router.

  • source
  • hideshow 4 child comments
  • load more comments (4 replies)
    load more comments
    view more: next β€Ί