>on laptop in kitchen
>music playing on workstation in office
>fiancee asks to turn it off

>ssh workstation -t 'sudo poweroff'

It's like 6ft away...

I love Linux, but its community can be so full of incompetent assholes..

Just now I asked in Freenode ##linux how to get the process ID of my current running process in bash. I got my answer - it's a shell built-in called "$$".

Then people start to nitpick some more - why do you need it? How is that different from an exit? - to which my response was.. well I know the whole idea behind exit codes, and I'd use it whenever possible, in all defined behavior that allows my program to terminate itself whenever it can. This pidfile however would be used to exit itself and provide diagnostic information whenever the program enters undefined behavior - a segfault in C language. Scenarios in which I don't have full control over the script's behavior anymore, such as the system entering an unworkable state where the system stalled, still got some binaries in RAM but the rootfs got unwritable, such as now - very helpfully, thanks HP! - when my laptop likely overheated and shat itself. I issued sudo reboot into it, but even that wouldn't issue properly anymore due to the /sbin/poweroff binary becoming inaccessible too. I had to issue a hard power cycle.. one of the few times in which I'm thankful to HP for actually causing shit like this, lol.

Point is, that undefined behavior is what I'm trying to mitigate against. I certainly can't let any files other than diagnostics remain in nonvolatile storage like that, especially when their state should be predictable in order to ensure good operation (like files expressing whether the script is already running or not, i.e. lock files).

Back to that IRC chat. Aside from the answer, I got ridicule from people who probably don't even know how to properly compile a kernel. Ubuntu users, overconfident scum. Sometimes I feel like I should ask questions in channels like #archlinux only, where such incompetency is ridiculed on its own.

sudo crontab -e
@reboot reboot

sudo poweroff

A ticking time bomb

ZShell is fun.
ZShell is educational.
It teaches you manners.
$> please poweroff

I fucked again...
This is second time I've accidentally executed sudo poweroff on test server via ssh assuming it was my machine :(

It's all because my mind was not stable as we were testing few issues on test server and at the same time from client side someone was doing the changes from Admin side(Wordpress) and we saw menu and few text got disappeared.
Such a bad day. smh

Windows not powering off when I press the shutdown button.

Mandatory long rant warning

Oh my fucking god, how many times have I lost my shit because of this fucking bullshit.

When I press the shutdown button, I want you to shut the fuck down you sorry excuse for an operating system.

Me and my friends want to hang out together, so I shut down my PC and walk over to their house, expecting an intense session of doing programming stuff and debating linux distros. Whatever the fuck we do when we get together.

I get to their house and pull out my laptop,, only its hot as fuck. And then I see it: the battery indicator is red. "What the balls?" I think to myself. I open the lid, and guess what?
WINDOWS DIDN'T FUCKING SHUT DOWN, AND IT STAYED ON THE POWERING OFF SCREEN ALL THIS FUCKING TIME. WHAT THE FUCK?
Now, my laptop has a bomb ass battery, so I didn't even bring a charger with me, and now I'm fucking stuck at a programming session with friends without a computer. FUCKING BULLSHIT.

If this was a one time thing, I wouldn't have cared so much, but this happened countless fucking times. Too many.

I would have deleted this cum socket of an operating system months ago if it weren't for the Windows exclusive software I need for school, and now that Steam supports games for linux, Windows has even less of an excuse to stay on my fucking laptop.

Windows is supposed be fucking simple, but linux takes it by a goddamn long shot. When I type "shutdown now" or "poweroff", linux shuts the fuck down, no questions asked. And if I ever need root permissions, I just type "sudo" instead of restarting the fucking program and requesting admin privileges.

Most of the software I use is compatible with both MacOS and Windows, and I already have Ubuntu installed on my laptop, so what do you guys think, should I butcher Windows off of my SSD and give MacOS a try?

Also, what is this magic? Ranting actually calmed me the fuck down... I need to start ranting more.

FUCK MICROSOFT AND FUCK WINDOWS, I WISH I COULD BURN TO FUCKING OBLIVION

>Be a customer
>Ask to reduce number of servers you rent at our company
>Agree to a date when the one server you no longer needs will be due to be disconnected and taken apart
>Date comes
>I have the honors of sending the final /sbin/poweroff
>All goes neatly... until...

The web that used to be there, now moved to another one of their machines, goes down, wtf???

Oh. a 500. What?
Checks logs...
Cannot connect to Database.
Wtf? Local database works... Oh. OH. OH MY GOD.

>Turn the server back on and tell the customer to fix the app to no longer connect to that machine

Sometimes, being a sysadmin can be a real fun!

Linux user versus:
"poweroff" vs "shutdown now"
"reboot" vs "shutdown -r now"

Is it just me or is systemd 240 royally fucked up?

My containers running Arch don't get connected to the network and systemd-networkd fails to start. On my laptop, the network is also unable to connect sometimes. And it consistently fails to complete shutdown without hard poweroff. The only viable temporary solution was rolling back to a snapshot in ALA that still has 239. Is that really supposed to be how a critical system component like the init is supposed to behave and get taken care of its issues?

Fuck QA, amirite 🤪.. seriously, that's even worse than Windows' "features" 😒

So I've been using the command "poweroff" to shut down my Linux system, tried searching only if this is safe or not, mostly people just speak of "shutdown -h now" or something like that. So my question is: Is it safe to shut down Linux using the "poweroff" command?

So I just started using FreeBSD(11.1) on an older laptop(T60) and while I was reading the handbook, it said that I should use "shutdown -p now". It didn't say anything about "poweroff", which I usually use on Linux to shut down the system, it does work in FreeBSD, but I don't know if it's safe. So does someone know whether it's safe or not?

so on my new lappy I'm testing XFS. After reading how bloody fast it is, I figured: why not give it a shot!

2 weeks later, I want to go back to ext4. XFS is SSSSOOOOOO fault-intollerant, it breaks my Chrome profile after each forced-poweroff (or power loss). And the on-boot fsck freezes. And after a successful bootup I see the log messages in syslog are all messed up (timestamps are all over the timeline!!!)

it's a mess... A very fast mess.

Tried rm -rf /* on my Red Hat Vm.
Was expecting the machine to go blank suddenly,but sadly nothing like that happened.

After sometime I stopped the process,and found that no command is executing, not even 'clear' or 'poweroff',lol.

I think deleting system32 in windows is more fun as it shuts down the machine suddenly. XD