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

    I don’t see an article linked for the relevant headline, but when I first installed linux (I use Arch btw) on my desktop, it didn’t come with swap auto-configured by the install helper ArchInstaller, but did come with oomkiller and also with 4/16GB of zram preconfigured. With three displays and three different kind of browsers open I ran out of memory when launching a game fairly quickly, and of course oomkiller went to town. Not only that, but because of stupid zram it also seemed to be stuck on an endless loop of not being able to kill something.

  • алсааас [she/they]@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    53
    ·
    edit-2
    7 hours ago

    This is blatantly false, 99% of Gnu/Linux distros actually have systemd nicely asking the processes to terminate themselves, it just doesn’t take longer than ~10 seconds usually.

    This meme would imply a sigkill.

    Edit: the distros that don’t use systemd likely don’t do any such thing either, I just don’t know about them.

  • FiveMacs@lemmy.ca
    link
    fedilink
    arrow-up
    52
    ·
    8 hours ago

    *clicks shut down on windows

    *goes to boot computer up into the morning… sees message ‘attempting to close programs’

    fu microsoft

  • henfredemars@infosec.pub
    link
    fedilink
    English
    arrow-up
    27
    ·
    edit-2
    8 hours ago

    Can I uninstall the bootloader Mr. Linux?
    Hell yes you can! Let’s try it and see what happens!

  • There are apps that don’t close gracefully when asked by systemd in my experience. I’ve often forgotten to close one and been stuck waiting 90s for a watchdog to timeout so the app gets killed.

    This is not a problem unique to windows.