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

help-circle

  • People keep saying that, but it isn’t true that the leak being in the disposable part of the vehicle means it’s not a safety problem.

    It’s the pressurisation system for the thrusters. If that fails, then they won’t be able to control the capsule until it hits the atmosphere. That could mean they get stuck on the ISS, in the most extreme case, or it could mean that they lose thrust mid-manouvre and they re-enter the atmosphere incorrectly. That could be anywhere from inconvenient (they miss their landing spot and someone has to come get them), to dangerous (they land so far away that they’re in danger of sinking or being eaten by bears before anyone reaches them) to outright fatal (they skip off the atmosphere, or tumble their way into reentry and burn up)





  • The problem is that their point is nonsense.

    This isn’t a long-standing problem being persistently ignored, this is a test flight designed specifically to discover such problems. They were so keen to test how the system handled problems like this that they deliberately damaged the heat shield before the flight (somewhere other than where this particular problem occurred).

    The implication that this partial failure of the heat shield is damning evidence of negligence is either ignorant or deliberately deceptive












  • MartianSands@sh.itjust.workstolinuxmemes@lemmy.worldsystemdeez nuts
    link
    fedilink
    arrow-up
    6
    arrow-down
    2
    ·
    edit-2
    2 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