• 0 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 27th, 2023

help-circle












  • MartianSands@sh.itjust.workstolinuxmemes@lemmy.worldsystemdeez nuts
    link
    fedilink
    arrow-up
    6
    arrow-down
    2
    ·
    edit-2
    7 months ago

    The default is as long as it is because most people value not losing data, or avoiding corruption, or generally preserving the proper functioning of software on their machine, over 90 seconds during which they could simply walk away.

    Especially when those 90 seconds only even come up when something isn’t right.

    If you feel that strongly that you’d rather let something malfunction, then you’re entirely at liberty to change the configuration. You don’t have to accept the design decisions of the package maintainers if you really want to do something differently.

    Also, if you’re that set against investigating why your system isn’t behaving the way you expect, then what the hell are you doing running arch? Half the point of that distro is that you get the bleeding edge of everything, and you’re expected to maintain your own damn system


  • 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



  • What they’re suggesting is to back up the whole disk, rather than any single partition. Anything you do to the partition to try and recover it has the potential to make a rescuable situation hopeless. If you have a copy of the exact state of every single bit on the drive, then you can try and fix it safe in the knowledge that you can always get back to exactly where you are now if you make it worse


  • It depends on what exactly gets cut or punctured, of course, but my understanding is that without proper surgical intervention it can be an exceptionally slow and painful way to die.

    The organs in the gut are mostly intestines. You’re not going to die just because they’ve spilled out, but you’re going to be bleeding pretty badly and if whatever caused them to spill out is still around then you’re pretty screwed.

    The bigger problem is that it’s unlikely they’ve just spilled out, they’re probably also sliced open. Now you’re in serious trouble, because there’s lots of blood in there so now you’re bleeding really badly. You’ve also got blood and the content of your digestives system mixing together, and that means some very nasty bacteria which are normally safely contained now have access to your blood.

    I suspect the most likely dangerous situation is a stab wound. In that case you’ll probably experience internal bleeding. There are no shortage of places for blood to go inside your body around there, including into your digestive system. I don’t think there’s anything much to stop blood from flowing endlessly into there, and you could bleed to death even if the external wound doesn’t look like it’s bleeding all that badly.

    In summary, getting stabbed in the gut will contaminate your blood and lead to potentially endless bleeding which can’t be treated with bandages because it’s inside. Even if you avoid bleeding to death, you’re probably going to die from a massive infection



  • MartianSands@sh.itjust.workstoSelfhosted@lemmy.worldWhy docker
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    1
    ·
    11 months ago

    I find it makes my life easier, personally, because I can set up and tear down environments I’m playing with easily.

    As for your user & permissions concern, are you aware that docker these days can be configured to map “root” in the container to a different user? Personally I prefer to use podman though, which doesn’t have that problem to begin with