So I’m working on a server from home.
I do a cat /sys/class/net/eth0/operstate
and it says unknown
despite the interface being obviously up, since I’m SSH’ing into the box.
I try to explicitely set the interface up to force the status to say up
with ip link set eth0 up
. No joy, still unknown
.
Hmm… maybe I should bring it down and back up.
So I do ip link set eth0 down
and… I drive 15 miles to work to do the corresponding ip link set eth0 up
50 years using Unix and I’m still doing this… 😥
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