What Are You Doing Right Now
-
@scottalanmiller said in What Are You Doing Right Now:
@Obsolesce said in What Are You Doing Right Now:
But I'm sure most admins have better things to do than to manually pull the uptime of each device in the terminal individually. No idea why that's even a discussion. If you are doing that, something already isn't right.
Well, in BASH it is a one liner to almost instantly get it from tons of machines. It's actually a pretty common task. In Windows, if you want the same report, it is very doable, but not quite as transparent.
But if you are logging into machines at all, then uptime remains a continuous thing you want.
Bash was designed to be THE interface to manage a Linux system. So yes, it was designed to manage the system with small simple commands that you use all day.
This want the case with PowerShell. Windows went a different direction. If you want a simple CLI with simple commands, use CMD. If you want a serious and powerful scripting language for Windows, use PowerShell. Nothing is better than that for Windows.
-
@Obsolesce said in What Are You Doing Right Now:
This want the case with PowerShell. Windows went a different direction. If you want a simple CLI with simple commands, use CMD. If you want a serious and powerful scripting language for Windows, use PowerShell. Nothing is better than that for Windows.
I don't agree here. CMD was simply left to languish. MS made it really, really clear that PS was the absolute final word in tooling for managing Windows. They stated this over and over again. And unlike Bash which was just a generic system that predated linux by decades, PS was custom built for this one purpose.
-
Steaming some veggies for me. Heating up some soup for Liesl.
-
Installing the latest Bash for Windows from MS to see how well it works.
-
@scottalanmiller said in What Are You Doing Right Now:
Installing the latest Bash for Windows from MS to see how well it works.
Not great. There's too much behind the scenes going on to make it anything you'd use outside of Dev or testing.
It's not apples to apples.
-
@Obsolesce takes forever to install, too.
-
@Obsolesce it has the uptime command, but because of some screwiness, it reports the time that the shell has been running and does not report the kernel run time. So the info from it is bad. In this day and age to have utilities report things like uptime wrong is pretty bad.
-
Learning how to deal with this
-
Video gaming with Liesl.
-
Funtimes with mp4 videos >(
-
Doing Ubiquiti updates through UNMS.
-
The kids are making some worms in dirt Jello pudding thing.
-
-
@scottalanmiller said in What Are You Doing Right Now:
At work, wishing I had that cup of worms while I wait for my coffee.
-
You are welcome to it. I tried a bite and it is totally bland.
-
@scottalanmiller said in What Are You Doing Right Now:
You are welcome to it. I tried a bite and it is totally bland.
Oh really?
-
@Obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
You are welcome to it. I tried a bite and it is totally bland.
Oh really?
Yeah, no one really wanted to eat it.
-
Just about to get the kids off to bed.
-
just got first cup of Coffee, Following up with a few sites.
Hey - How do you send commands to printers on com ports - to test printing?
-
@WrCombs said in What Are You Doing Right Now:
just got first cup of Coffee, Following up with a few sites.
Hey - How do you send commands to printers on com ports - to test printing?
You get a new printer...
Even I don't know if that's more of a joke, serious recommendation, or both.
I don't think there is any special command. No printout = serial port settings are probably wrong. Does the printer react at all when you try to send it a print job?
