For context, parent comment is trying to decipher this heavily-PR-reviewed paragraph:
> During one of these routine maintenance jobs, a command was issued with the intention to assess the availability of global backbone capacity, which unintentionally took down all the connections in our backbone network, effectively disconnecting Facebook data centers globally. Our systems are designed to audit commands like these to prevent mistakes like this, but a bug in that audit tool didn’t properly stop the command.
Seems like it. It's kinda like typing hostname and accidentally poking your yubikey (Not that I've done that...) or the date command that both let's you set the date and format the date
For context, parent comment is trying to decipher this heavily-PR-reviewed paragraph:
> During one of these routine maintenance jobs, a command was issued with the intention to assess the availability of global backbone capacity, which unintentionally took down all the connections in our backbone network, effectively disconnecting Facebook data centers globally. Our systems are designed to audit commands like these to prevent mistakes like this, but a bug in that audit tool didn’t properly stop the command.
s/assess/augment/g
Seems like it. It's kinda like typing hostname and accidentally poking your yubikey (Not that I've done that...) or the date command that both let's you set the date and format the date
(or some variation thereof)
My guess : he executed the command from shell history. Commands look similar enough and he hit Enter too quickly
But why would the clear command be in their history?
cltr+r mpls [enter]
Would fit muscle memory, but if that wasn't caught by the automated tool they have some work to do.