• MammutX@europe.pub
    link
    fedilink
    arrow-up
    4
    ·
    1 hour ago

    and this how I deleted the file I edited the entire day: shutdown -h now. No go to bed NOW!

  • Realitätsverlust@lemmy.zip
    link
    fedilink
    English
    arrow-up
    32
    arrow-down
    1
    ·
    3 hours ago

    Linux does give every application time to shut down correctly, but unlike windows, it won’t wait for ages until every process is down. Linux WILL shut down in a certain timeframe, whereas windows waits for years if necessary. In my old job, we all had to use windows and I had times where I clicked shut down, turned off my monitor, grabbed my stuff, left and in the next morning, the PC was still on because Notepad refused to just close lmao.

    • WIZARD POPE💫@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      1 hour ago

      That is what infuriates me so much. Instead of just killing the process after 5 mins of waiting it just cancels the shutdown. Like fuck off with that shit.

  • h4x0r@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    14
    ·
    3 hours ago
    $ kill -L
     1) SIGHUP	 2) SIGINT	 3) SIGQUIT	 4) SIGILL	 5) SIGTRAP
     6) SIGABRT	 7) SIGBUS	 8) SIGFPE	 9) SIGKILL	10) SIGUSR1
    11) SIGSEGV	12) SIGUSR2	13) SIGPIPE	14) SIGALRM	15) SIGTERM
    16) SIGSTKFLT	17) SIGCHLD	18) SIGCONT	19) SIGSTOP	20) SIGTSTP
    21) SIGTTIN	22) SIGTTOU	23) SIGURG	24) SIGXCPU	25) SIGXFSZ
    26) SIGVTALRM	27) SIGPROF	28) SIGWINCH	29) SIGIO	30) SIGPWR
    31) SIGSYS	34) SIGRTMIN	35) SIGRTMIN+1	36) SIGRTMIN+2	37) SIGRTMIN+3
    38) SIGRTMIN+4	39) SIGRTMIN+5	40) SIGRTMIN+6	41) SIGRTMIN+7	42) SIGRTMIN+8
    43) SIGRTMIN+9	44) SIGRTMIN+10	45) SIGRTMIN+11	46) SIGRTMIN+12	47) SIGRTMIN+13
    48) SIGRTMIN+14	49) SIGRTMIN+15	50) SIGRTMAX-14	51) SIGRTMAX-13	52) SIGRTMAX-12
    53) SIGRTMAX-11	54) SIGRTMAX-10	55) SIGRTMAX-9	56) SIGRTMAX-8	57) SIGRTMAX-7
    58) SIGRTMAX-6	59) SIGRTMAX-5	60) SIGRTMAX-4	61) SIGRTMAX-3	62) SIGRTMAX-2
    63) SIGRTMAX-1	64) SIGRTMAX
    
  • astrsk@fedia.io
    link
    fedilink
    arrow-up
    42
    ·
    4 hours ago

    If your app doesn’t respond to SIGTERM gracefully, you need to fix your app. The system did its job as documented.

    • Jakeroxs@sh.itjust.works
      link
      fedilink
      arrow-up
      6
      ·
      4 hours ago

      I’ve tried to turn a pc off to go to sleep, only to realize in the morning it’s still on because some program refused to close.

      Now when I see the prompt to force close, I just say yes.

  • chronicledmonocle@lemmy.world
    link
    fedilink
    arrow-up
    87
    ·
    8 hours ago

    Linux gives processed a chance to gracefully close. However, it also will absolutely NOT allow a process to hang up the shutdown or restart procedure after a point. If you’re using systemd (which there is a good chance you are), it’ll count down. If the process hasn’t stopped in the time allotted, it gets Old Yellered.

  • Raltoid@lemmy.world
    link
    fedilink
    arrow-up
    260
    arrow-down
    4
    ·
    edit-2
    12 hours ago
    1. Linux normally does a nice shutdown as well, unless you force it.

    2. You can force it on windows if you really want.

    I’m so tired of linux memes posted/made by people who don’t know much about windows or linux.

    • derpgon@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      1 hour ago
      1. Linux programs either HAVE to be quick while receiving shutdown signal, otherwise the state will be fucked, work will be lost, and people will be mad, and program will stop being used.

      2. Clicking the Windows button to force shutdown will straight up kill the program and won’t care at all.

    • Shanmugha@lemmy.world
      link
      fedilink
      arrow-up
      10
      arrow-down
      3
      ·
      edit-2
      4 hours ago

      Oh, p-lease, can force it my ass, Linux has never failed to shutdown on me when using plain obvious GUI method. windows - can easily hang on forever as long as computer stays powered. The point of all the memes is exactly insane windows defaults, not the things that can or can’t be done by someone with enough knowledge

    • cmgvd3lw@discuss.tchncs.de
      link
      fedilink
      arrow-up
      30
      arrow-down
      1
      ·
      edit-2
      9 hours ago

      Absolutely, if people agree or not, the core windows is still a pretty powerful operating system. Its sad that they are ruining it by adding crap into it.

      • madame_gaymes@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        edit-2
        2 hours ago

        There’s also a hardware way, works on practically any device. Phone, tablet, laptop, desktop, etc. Doesn’t matter what the OS is.

        Press and hold power button for anywhere between 5 - 15 seconds. The second half of this meme describes this method the best, methinks.

        • criticon@lemmy.ca
          link
          fedilink
          arrow-up
          9
          ·
          7 hours ago

          Some clarification of the command

          -r #restart

          -s #shutdown

          -t 00 #wait 0 seconds

          -f #forced

            • Laurel Raven@lemmy.zip
              link
              fedilink
              English
              arrow-up
              4
              ·
              4 hours ago

              I can’t speak for them if they’re joking or not but it’s something you can absolutely do. *.bat files (short for “batch”, as in a batch of commands to execute in sequence) are the script files for the Windows command line, and can be executed by double clicking on them

              • jmacapp@lemm.ee
                link
                fedilink
                arrow-up
                1
                ·
                4 hours ago

                Thanks, I’m familiar with batch files. This just seems like a very bad way to perform a shutdown, especially when running a UI Desktop windowing system. And even if that shutdown command is fully supported from the GUI, I would guess you need to be admin to run it, which means you can run the bat file as admin, so if you can edit the file or modify the env in which it runs (e.g. PATH) it seems like it could be a security problem. And if you don’t need to be root to run the shutdown command, that seems like its own problem. I suppose Windows still has the “run as administrator” from the context menu so maybe that helps.

                • Sonicdemon86@lemmy.world
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  ·
                  2 hours ago

                  As it is a simple command you don’t need to be an admin or run as administrator. Listen kids don’t run batch files if you don’t know where they came from or who made them.

        • kewko@sh.itjust.works
          link
          fedilink
          arrow-up
          6
          arrow-down
          7
          ·
          10 hours ago

          If -t is specified -f is assumed and redundant, but also it will try to do graceful l, but with a patience of a cranky toddler

          • aeiou_ckr@lemmy.world
            link
            fedilink
            arrow-up
            17
            ·
            10 hours ago

            Not really. If -f (force) is removed windows will shutdown similar to pressing the shutdown button and will wait for your input regarding open programs. -f is needed to just just “do it” with no hesitation or response from the user.

            • kewko@sh.itjust.works
              link
              fedilink
              arrow-up
              4
              arrow-down
              5
              ·
              edit-2
              9 hours ago

              Straight from the doc

              /t <xxx> Sets the time-out period before shutdown to xxx seconds. The valid range is 0-315360000 (10 years), with a default of 30. If the timeout period is greater than 0, the /f parameter is implied.

              • Lupus@feddit.org
                link
                fedilink
                arrow-up
                24
                ·
                9 hours ago

                Sooo when you use the prompt

                Shutdown.exe -r -t 00

                You would need the -f since we defined the timeout period as 0. Because:

                If the timeout period is greater than 0, the /f parameter is implied.

      • Dave@lemmy.nz
        link
        fedilink
        arrow-up
        15
        ·
        11 hours ago

        The process manager lets you kill any process.

        You can also click the do it anyway button when it’s waiting on shutdown, but I’ve had less consistent success with that.

    • Apytele@sh.itjust.works
      link
      fedilink
      arrow-up
      8
      ·
      11 hours ago

      It was simpler using Linux to just kill things unceremoniously, but my coworkers are also consistently amazed when Epic throws a temper tantrum (rare, but it happens) and I walk over and ctrl-alt-delete and tell it to sit down and shut the fuck up until it’s ready to reboot and act right.

      • swab148@lemm.ee
        link
        fedilink
        English
        arrow-up
        13
        ·
        7 hours ago

        He wrote Pulseaudio, Avahi, and systemd before joining Microsoft, where he currently works.

          • silasmariner@programming.dev
            link
            fedilink
            arrow-up
            5
            ·
            6 hours ago

            One task lifecycle management tool to bring them all, one tool to find them. One tool to rule them all and in the darkness bind them.

            • acockworkorange@mander.xyz
              link
              fedilink
              arrow-up
              3
              ·
              edit-2
              4 hours ago

              Great talk indeed. And I will quickly acknowledge that something had to be done, and that systemd had the courage to innovate and address the issues. I just wish it did so in a more transparent way to the end user.

              For instance: there’s a whole established system of dealing with logs in place. Why build a separate one just for your init system? Why binary? Why even integrate it with your init? I’m not saying storing everything on /var/log and using logrotate is ideal or even covers all use cases. But a log management system is its own thing.

              That’s just an example of how systemd didn’t jive with every other subsystem in a Unix like OS. It could have been done in a Unix way - small cohesive tools that are good at one job and can be combined to do more together.

              That’s where I think he missed the mark when dismissing the monolithic criticism by saying “it’s not a single binary so it’s not monolithic”. Its philosophy is monolithic.

              That said, I use systemd on my machines because that’s what my do uses and I don’t think it’s a reason to swap distros. For the same reason I use Linux and not a micro kernel. I.e. philosophy is important, but implementation is importanter.

              • BCsven@lemmy.ca
                link
                fedilink
                arrow-up
                1
                ·
                2 hours ago

                While monolithic may not be the keep is simple rule aimed for in originally in Unix/Linux, I wonder if it even matters…is there something really gained by init systems that make a difference for the average Linux user?

      • Azzu@lemm.ee
        link
        fedilink
        arrow-up
        4
        ·
        edit-2
        5 hours ago

        systemd moment in the sense that someone not affiliated with systemd used systemd to write a stop job that doesn’t terminate quickly? Or that you willingly installed software that brought along a slow stop job with it?

        This is like so far away from systemd’s fault, idk, it must just be a meme right?

        • juipeltje@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          4 hours ago

          Pretty sure i’ve had this happen with services i didn’t even create, but yeah it was just a joke, i don’t care about init systems, but i don’t recall this ever happening when i was using runit.

          • Azzu@lemm.ee
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            3 hours ago

            I don’t know runit. Maybe runit didn’t even have a way to delay or customize shutdown, maybe it always just waits 5 seconds and then forcibly terminates a process, resulting in you never noticing when a cleanup job was too slow. Maybe you just randomly never installed a particular program with a slow shutdown job while using runit. There’s a bunch of reasonable explanations and possibilities for why this difference exists, and they can all mean systemd is perfectly reasonable.

            • juipeltje@lemmy.world
              link
              fedilink
              arrow-up
              2
              ·
              2 hours ago

              Alright man, fact remains i was just making a silly joke, you don’t have to be poettering’s pr team lol

              • Azzu@lemm.ee
                link
                fedilink
                arrow-up
                1
                ·
                32 minutes ago

                You’re the one who brought up runit and insinuated it doesn’t have this problem ¯_(ツ)_/¯

    • DannyBoy@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      8
      ·
      8 hours ago

      Not only do I get this on shutdown I get a job on startup that runs for a minute thirty that looks for a swap partition that I have deleted.

      • B-TR3E@feddit.org
        link
        fedilink
        arrow-up
        5
        ·
        edit-2
        7 hours ago

        Did you delete it or comment it out in /etc/fstab? Adding

        noresume
        

        to your boot arguments should also help. You can try that out in “extended options” during boot and add it to /boot/grub/grub.cfg later. Don’t forget to run

        update-grub
        

        after editing.

        • DannyBoy@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          3
          ·
          6 hours ago

          Yeah I just deleted the swap partition without updating anything. I’ve realized since then I need to update the fstab but I never think about it until the odd time I do a full reboot.

      • BCsven@lemmy.ca
        link
        fedilink
        arrow-up
        3
        ·
        7 hours ago

        As comments below you will need to check /etc/fstab and then run a mkgrub or mkgrub2 command with options like -o (you will have lookup the full string) and it will rewrite the info that the system is told at boot about drive partitions

      • alt_xa_23@lemmy.world
        link
        fedilink
        arrow-up
        5
        ·
        8 hours ago

        I’ve had that problem before, I think I had to mess around with my fstab and grub config to fix it.