• Chronographs
          link
          fedilink
          English
          arrow-up
          5
          ·
          6 months ago

          “Failed over” does, I’ve never heard fell over mean anything but what’s described in the picture.

          • Ephera@lemmy.ml
            link
            fedilink
            arrow-up
            2
            ·
            6 months ago

            I have heard it before, albeit tongue-in-cheek. So, like the server can be “running”, it can also trip and fall over.

        • bamboo@lemm.ee
          link
          fedilink
          arrow-up
          2
          ·
          6 months ago

          I use it to describe a variety of things, but usually it’s related to servers not being able to handle load rather than an outright crash, but I’m not strict about it. Laos balancer failures could be it, could also just be that something was really I efficient but wasn’t noticed until it went into production.

        • Revan343@lemmy.ca
          link
          fedilink
          arrow-up
          2
          ·
          6 months ago

          Some bands of old-time hackers figured out how to induce disk-accessing patterns that would do this to particular drive models and held disk-drive races.

          I love the Jargon File

    • Mouselemming@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      6 months ago

      That’s probably fallout from the early days of this joke. After seeing this image with ‘the server crashed’, funny programmers would start saying their server “fell over” to reference that memory. Now it’s come full circle. Meanwhile those of us who are “grandma peering at the computer screen” would only say a computer has “crashed.” And wouldn’t know how to fix it beyond a couple of tries at turning it off and back on again. (Which usually does work, though!)