this post was submitted on 18 Feb 2025
265 points (99.3% liked)
Linux
50359 readers
1434 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by AlpΓ‘r-Etele MΓ©der, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Why don't you use chained commands, or better yet simply create an alias that chains down/up, then use the alias instead?
Because I plain forgot I was remote. It's as simple and as stupid as that.
We've all been there. If you do this stuff for a living, you've done that way more than once.
Fair enough. I've done worse in my time as a keyboard jockey.
That is why you have KVMs..
That is a totally fair explanation. End of story. No blame. Honest mistake.
time to setup a console server so that you don't do that again.
Until they have to troubleshoot the console server ..
then setup a super console server. lol
I have once actually used a console server console server to troubleshoot a misbehaving console server.
i once worked at a place that had something like this and; it sounds silly; but i got a live demonstration that it was the smartest thing ever.
It's console servers all the way down (up?)
and you make each one geographically closer than the previous one until there's one right next to you. lol
So that's why we have mobile phones
so long as you're mobile, any phone can become a mobile phone. lol
Nah, you only need two, each connected to the other. Use one to work on the other.
Or use some kind of molly guard. Or have an OOB management channel.
You'd think you'd learn from your mistakes after one or two of them, not fifty years' worth...
Don't be shitty.
In my defense, I just installed the machine. I was configuring it from home after hours.
I've configured PAM to not let me login remotely after hours, because I just know that someday I'll want to fix "just this tiny thing" and I'll break production because I'm too tired. I clearly need protection from myself, and this is one slice in Dr.Reasons's Swiss cheese model.
Don't let the people drag you down, this happens to all of us.
Harsh (to yourself), but fair
Yes, that what you'd think. And then you'll sit with a blank terminal once again when you did some trivial mistake yet again.
A friend of mine developed a habit (working on a decent sized ISP 20+ years ago) to set up a scheduled reboot for everything in 30 minutes no matter what you're going to do. The hardware back then (I think it was mostly cisco) had a 'running conrfig' and 'stored config' which were two separate instances. Log in, set up scheduled reboot, do whatever you're planning to do and if you mess up and lock yourself out the system will restore to previous config in a while and then you can avoid the previous mistake. Rinse and repeat.
And, personally, I think that's the one of the best ways to differentiate actual professionals from 'move fast and break things' group. Once you've locked yourself out of the system literally half way across the globe too many times you'll eventually learn to think about the next step and failovers. I'm not that much of a network guy, but I have shot myself in the foot enough that whenever there's dd, mkfs or something similar on the root shell I automatically pause for a second to confirm the command before hitting enter.
And while you gain experience you also know how to avoid the pitfalls, the more important part (at least for myself) is to think ahead. The constant mindset of thinking about processes, connectivity, what you can actually do if you fuck up and so on becomes a part of your workflow. Accidents will happen, no matter how much experience you have. The really good admins just know that something will go wrong at some point in the process and build stuff to guarantee that when you fuck things up you still have availability to fix it instead of calling someone 6 timezones away in the middle of the night to clean up your mess.
Without repeating my other comment. This approach saved my life many times