« first day (3909 days earlier)      last day (1047 days later) » 

2:18 AM
@FaheemMitha If the CPU gets too hot, it'll automatically shut down. That's a feature built into the CPU itself so no software bug can override it. Of course, high temperatures do reduce the lifespan of hard drives, but generally you can't overheat a computer in one go without installing it seriously incorrectly.
 
3:01 AM
what happens if someone runs sudo rm -rf / ?
I am aware it's bad btw
I wasnt trying to get anyone to do it
I'm just wondering if it will really mess up my computer or if there are some extra safety measures
 
 
1 hour later…
4:06 AM
24
Q: How far can you go with rm -rf / as root

Sudipta ChatterjeeIf you are root, and you issue rm -rf / Then how far can the command go? Can you recover data from this kind of an action? Even after the binaries are gone, would the running processes still be active? What would it take to make the same physical machine boot again? What files would you need...

149
Q: Monday morning mistake: sudo rm -rf --no-preserve-root /

Jonas Bylov Please note: The answers and comments to this question contains content from another, similar question that has received a lot of attention from outside media but turned out to be hoax question in some kind of viral marketing scheme. As we don't allow ServerFault to be abused in such a way, t...

 
 
4 hours later…
8:37 AM
@MichaelHomer is the tag part of the viral marketing? I'm surprised to see it there.
 
I don't expect they merged the tags from the question they deleted
 
probably not
 
8:59 AM
@forest I thought this was a feature of Intel, but not of AMD. Though this might be something that was true once, but not now.
 
Aug 21 '20 at 14:07, by Stephen Kitt
@FaheemMitha yup, AMD fixed that a couple of decades ago IIRC — it was a problem with the first K7s ;-)
We’ve discussed this in the past ;-)
 
@StephenKitt Ah, yes. And only a year ago. Give or take.
Well, I'll try to retain the information on this second goaround.
 
 
8 hours later…
5:06 PM
@ibuprofen Yes, that's more or less what I meant.
 
 
3 hours later…
7:47 PM
1
Q: script with `read` in bash while loop causing high CPU usage when run as a systemd service

seamuxI wrote a script to run specific actions conditional on input events informed by an event monitor, which looks something like $ cat script.sh ----------------------------------------------------------- #!/usr/bin/bash stdbuf -oL /usr/bin/event_monitor | while IFS= read LINE do something with...

There has to be something obvious we're missing there.
 
8:01 PM
"Don't use bash for that..."
 
@jesse_b Why not? You mean use a simple POSIX shell instead?
 
@terdon I dunno, I rarely go a month without being met with you guys telling me not to use bash/read to parse files because of inefficiencies. Now someone is using bash/read to parse a file and complaining about lack of efficiency
 
Eh, true, but not exactly a file as such. And very basic parsing.
 
I wonder if it's because read exits 1 so systemd thinks the script failed and tries to restart it every time it exits
I guess that would create new pids though
 
8:23 PM
I think Stéphane's comment from a few minutes ago, there, makes a good point (thanks to the OP confirming the straced, endlessly reading process is that event_monitor).
 
> 90C is TjMax for that CPU
So it looks like it does have that.
 
 
3 hours later…
11:50 PM
Feels like digging a deep hole here ... too much at once?
0
A: How can a subshell return data in a variable (not file) and output distinct logs at the same time?

ibuprofenThis should be OK: #! /bin/bash - doSomething() { print_err "About to do something" a="$(doSomethingElse)" if [[ "$a" = "dog" ]]; then print_err "Worked" print_err "Now let's do xyz" printf '%s' "cat" else print_err "failed for some reason" ...

 

« first day (3909 days earlier)      last day (1047 days later) »