• FigMcLargeHuge@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    2 months ago

    A guy in our data center couldn’t figure out who owned a particular machine that he needed to work on. So his solution to figure it out was to let them come to him. He went and pulled out the network cable and waited. He was escorted out a little while later. The moral of the story is don’t go disabling production machines on purpose.

    • ramble81@lemm.ee
      link
      fedilink
      arrow-up
      0
      ·
      2 months ago

      Honestly we do that when we ask and no one speaks up. Lovingly called the “scream test” as we wait to see who screams.

      • FigMcLargeHuge@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 months ago

        I guess it depends on where you work. This was a large datacenter for a very large health insurance company. They made it a point later that day to remind people that it was a fireable offense to mess with production machines like that on purpose. And evidently the service he disabled was critical enough that it didn’t take long for the hammer to come down. There were plenty of ways to find out who owned the machine, he just chose the easiest and got fired on the spot for it.