WTF Bites
-
@loopback0 said in WTF Bites:
that is, the downvotes are supposed to say boomzilla whatever the number of times the downvote count is, not any other user
The user it shows instead of the real downvoter is configurable - it's currently Mason_Wheeler but it's been others in the past.
Yep, as it pleases my whims. However, I can confirm that is wasn't Mason doing the downvoting there.
-
LOL. The salt is strong with this one.
Yeah, @Mason_Wheeler downvoted like every single post in that chain. Is they always like that?
Yes and no. Downvotes are anonymous and (probably for reasons of this being a hacked on feature by us) are always shown by the same user. Even multiple downvotes will show the same user.
It used to be that all downvotes are @boomzilla, but since @DogsB kept complaining that he wants to be the face of downvotes, it got shuffled around to anyone but him. It finally settled on MW because, um, he has certain tendencies making this a good zeroth order approximation.But in this case it’s probably not him.
-
LOL. The salt is strong with this one.
Yeah, @Mason_Wheeler downvoted like every single post in that chain. Is they always like that?
Yes and no. Downvotes are anonymous and (probably for reasons of this being a hacked on feature by us) are always shown by the same user. Even multiple downvotes will show the same user.
It used to be that all downvotes are @boomzilla, but since @DogsB kept complaining that he wants to be the face of downvotes, it got shuffled around to anyone but him. It finally settled on MW because, um, he has certain tendencies making this a good zeroth order approximation.But in this case it’s probably not him.
Thanks for reminding me. Fucking mods warthogiest of warthogs would have given it to me now.
-
probably for reasons of this being a hacked on feature by us
IIRC, the window is normally mod-only and general consent preferred downvotes to be anonymousse?
-
@boomzilla said in WTF Bites:
LOL. The salt is strong with this one.
Yeah, @Mason_Wheeler downvoted like every single post in that chain. Is they always like that?
Hmm...is that correct? Shouldn't it be "Are they always like that?"
Of course, that's still less correct than "Is he always like that?"
You're using question' marks wrong, them's for sure.
-
@boomzilla said in WTF Bites:
LOL. The salt is strong with this one.
Yeah, @Mason_Wheeler downvoted like every single post in that chain. Is they always like that?
Hmm...is that correct? Shouldn't it be "Are they always like that?"
Of course, that's still less correct than "Is he always like that?"
You're using question' marks wrong, them's for sure.
I WASN'T ASKING FOR PUNCTUATION HELP
-
-
@boomzilla said in WTF Bites:
LOL. The salt is strong with this one.
Yeah, @Mason_Wheeler downvoted like every single post in that chain. Is they always like that?
Hmm...is that correct? Shouldn't it be "Are they always like that?"
Of course, that's still less correct than "Is he always like that?"
So @Mason-Wheeler is he/him. I knew someone would reply.
-
@loopback0 said in WTF Bites:
that is, the downvotes are supposed to say boomzilla whatever the number of times the downvote count is, not any other user
The user it shows instead of the real downvoter is configurable - it's currently Mason_Wheeler but it's been others in the past.
I can't wait for it to be my turn and the dismay and chaos reigns!
-
@boomzilla said in WTF Bites:
@boomzilla said in WTF Bites:
LOL. The salt is strong with this one.
Yeah, @Mason_Wheeler downvoted like every single post in that chain. Is they always like that?
Hmm...is that correct? Shouldn't it be "Are they always like that?"
Of course, that's still less correct than "Is he always like that?"
You're using question' marks wrong, them's for sure.
I WASN'T ASKING FOR PUNCTUATION HELP
Signs you spend to much time on WTDWTF, #0xb0: you consider "YOUR RONG!!!!11" too helpful.
-
@boomzilla said in WTF Bites:
LOL. The salt is strong with this one.
Yeah, @Mason_Wheeler downvoted like every single post in that chain. Is they always like that?
Hmm...is that correct? Shouldn't it be "Are they always like that?"
Of course, that's still less correct than "Is he always like that?"
Pronouns :motherfucker:. Hast thou heard of singular they?
-
@boomzilla said in WTF Bites:
LOL. The salt is strong with this one.
Yeah, @Mason_Wheeler downvoted like every single post in that chain. Is they always like that?
Hmm...is that correct? Shouldn't it be "Are they always like that?"
Of course, that's still less correct than "Is he always like that?"
Pronouns :motherfucker:. Hast thou heard of singular they?
I have, but they've always been conjugated differently than "he." Like I just did.
-
UnRAID's helpful display of CPU load:
-
-
@Polygeekery That's a lot of CPU overload, really a lot of it!
Are you mining bitcoins?
-
@BernieTheBernie no. Docker was hung and refusing to stop its fuckery. Couldn't kill it. Docker logs were also using near as makes no difference 100% of the memory. The machine refused to reboot. SSH windows kept locking up, including two that hung when attempting to reboot the machine. Disks would not unmount. It was looking like I was going to have to yank the physical plug to get it to reboot.
After lots of shenanigans, including multiple attempts to kill processes keeping the disks busy so that they would not unmount, I once again tried:
fuser -mvk /mnt/disk*A shit ton of scrolling later, as opposed to locking up another SSH window as had previously happened, all my SSH connections terminated and hopefully it comes back up in a bit.
Fucking Docker. I goddamn hate Docker. This is probably the third time that I have had it hang like this where it won't kill a container that is misbehaving and it keeps respawning shit with rapidly changing PIDs. To be fair, the container is one of my own so I am probably to blame, but I still hate Docker.
-
@Polygeekery said in WTF Bites:
I am probably to blame, but I still hate __________________.
Fill in the blank. We've all been there.
-
@Polygeekery said in WTF Bites:
hopefully it comes back up in a bit.
Hope in one hand, shit in the other.......
I guess I get to go to the basement and yank the plug while praying that I don't have to restore >40TB of data when UnRAID's "basically RAID4, but not technically RAID4" shits itself.
-
@Polygeekery said in WTF Bites:
It was looking like I was going to have to yank the physical plug to get it to reboot.
There is always the
echo b > /proc/sysrq-trigger. And if you want to be a bit nicer,echo usb > /proc/sysrq-trigger(ok, I am not sure it will do them in sequence or if you have to do it as three separate commands; I never did the combo on server, only on keyboard (u to remount everything read-only, s to sync and b to reboot; you need to be logged in as root).
-
@Polygeekery said in WTF Bites:
Fucking Docker. I goddamn hate Docker.
Some time ago when we were setting up openshift, a version that was nearly obsolete already and based on brutally obsolete centos 7 and docker 1.13 I've seen a fair share of random lock-ups with docker simply losing control of some containers and stopping to respond whenever asked to do anything about them. Not seen that with newer versions though. I think 17.05 was the first that can be actually considered production ready.
This is probably the third time that I have had it hang like this where it won't kill a container that is misbehaving and it keeps respawning shit with rapidly changing PIDs. To be fair, the container is one of my own so I am probably to blame, but I still hate Docker.
Well, problems happen, which is why all versions of init (sysv init, upstart, systemd) have a rate limit for startup—if the service stops several times in quick succession, it will not try to start it again for a couple of minutes so you can diagnose what's wrong. It sounds like Docker is too dumb and keeps restarting a broken container that I suppose you created with
--restart=Alwaysas fast as it can—and because it is--restart=Always, it will restart if when youkillit too—stopmight work (but I don't know, really), if not, you'd have torm -fit.I'd suggest going either
- the kubernetes (k3s or microk8s) route; it's more to learn, but then you'll be using the same tools if you ever want to go multiple nodes.
- the podman+systemd route; if you intend to stay on single Linux server, podman starts the container directly from the command without a daemon (and can do it as non-root in subusers; better for security) and you just let systemd start it—with all the benefits of proper failure handling systemd provides.
-
Well, problems happen, which is why all versions of init (sysv init, upstart, systemd) have a rate limit for startup—if the service stops several times in quick succession, it will not try to start it again for a couple of minutes so you can diagnose what's wrong. It sounds like Docker is too dumb and keeps restarting a broken container that I suppose you created with
--restart=Alwaysas fast as it can—and because it is--restart=Always, it will restart if when youkillit too—stopmight work (but I don't know, really), if not, you'd have torm -fit.That is my guess also. I tried
docker kill offending_containermultiple times and it refused to die. So I attempted tokill -9the container PID but it would change before I had a chance to. Then I trieddocker stop $(docker ps -a -q)which also did not work so then I moved on to trying to kill the Docker service itself which would only result in a hung SSH section and then moved back to trying to kill the containers withpkilland a lot of other shit. I eventually moved on to trying toumountthe drives hoping that I could then successfully reboot. That ended up eventually working. Currently doing a parity check which will probably take a couple of days, but all the drives came back up and mounted so it is probably fine. If not I guess I get to restore my data via nine 8TB external drives.
I'd suggest going either
the kubernetes (k3s or microk8s) route; it's more to learn, but then you'll be using the same tools if you ever want to go multiple nodes.
the podman+systemd route; if you intend to stay on single Linux server, podman starts the container directly from the command without a daemon (and can do it as non-root in subusers; better for security) and you just let systemd start it—with all the benefits of proper failure handling systemd provides.This is a home server running UnRAID and a few Docker containers for media handling and such. It is a storage server. Downtime vs dollars is on the wrong side of the equation for any of that to make sense in this application.
k3s
I have never seen it written that way. I have always seen it as "K8s". I am too
to look it up and also too apathetic to care.
-
@Polygeekery said in WTF Bites:
I'd suggest going either
the kubernetes (k3s or microk8s) route; it's more to learn, but then you'll be using the same tools if you ever want to go multiple nodes.
the podman+systemd route; if you intend to stay on single Linux server, podman starts the container directly from the command without a daemon (and can do it as non-root in subusers; better for security) and you just let systemd start it—with all the benefits of proper failure handling systemd provides.This is a home server running UnRAID and a few Docker containers for media handling and such. It is a storage server. Downtime vs dollars is on the wrong side of the equation for any of that to make sense in this application.
I would say the podman+systemd would make sense here. You replace docker with podman—podman is a drop-in replacement for docker (with some extra options and commands)—, set up the container and use podman generate systemd to spit out a unit that you drop in systemd—which you already should have because all recent Linux distributions do—to take care of the restarting properly.
k3s
I have never seen it written that way. I have always seen it as "K8s". I am too
to look it up and also too apathetic to care.k3s != k8s (but k3s ⊂ k8s)—a specific light-weight installer of kubernetes that you can drop in to a linux box and it mostly just runs without much hassle.
-
@Polygeekery said in WTF Bites:
Fucking Docker. I goddamn hate Docker.
I used to be quite indifferent to Docker. Then people made me use it. I now share your opinion on Docker.
-
Some time ago ... brutally obsolete centos 7
Probably about the time we were starting to upgrade from Centos 5 to 6.
-
with all the benefits of proper failure handling systemd provides
You're sick, mister.
-
@HardwareGeek said in WTF Bites:
@Polygeekery said in WTF Bites:
I am probably to blame, but I still hate __________________.
Fill in the blank. We've all been there.
Not me. When I forkbomb a machine I do it on purpose.
-
@Polygeekery said in WTF Bites:
Fucking Docker. I goddamn hate Docker.
I used to be quite indifferent to Docker. Then people made me use it. I now share your opinion on Docker.
I use containers, but I did mostly migrate away from Docker for running them.
-
Well, problems happen, which is why all versions of init (sysv init, upstart, systemd) have a rate limit for startup—if the service stops several times in quick succession, it will not try to start it again for a couple of minutes so you can diagnose what's wrong.
Funny coincidence, the exact thing I was just trying to slack off from when I came to read this thread was a faulty container that crashed in the entrypoint and systemd was set to
Restart=always.
You can configure it withStartLimitIntervalSecandStartLimitBurst, but if you forget it, no rate limiting for you.
-
I think 17.05 was the first that can be actually considered production ready.
I don't think that I would consider any Docker version to be production ready.
That being said, we have been using it in production for a fair bit of time.
-
You can configure it with
StartLimitIntervalSecandStartLimitBurst, but if you forget it, no rate limiting for you.I almost want to know the rationale for not including sane defaults of non-zero values, but then this is Docker we're talking about.
-
@Tsaukpaetra said in WTF Bites:
You can configure it with
StartLimitIntervalSecandStartLimitBurst, but if you forget it, no rate limiting for you.I almost want to know the rationale for not including sane defaults of non-zero values, but then this is Docker we're talking about.
We can't be, because
StartLimitIntervalSecandStartLimitBurstare systemd parameters. Docker does not have them.…
Funny coincidence, the exact thing I was just trying to slack off from when I came to read this thread was a faulty container that crashed in the entrypoint and systemd was set to
Restart=always.
You can configure it withStartLimitIntervalSecandStartLimitBurst, but if you forget it, no rate limiting for you.Can you clarify it a bit? Systemd does not start containers, it starts services. The service might run a container, but it must do that through some tool—either docker, containerd or podman. If it does it through one of the former two, they may (don't have to, but usually do) restart the container themselves. In which case the systemd parameters only apply to start of the docker and/or containerd service and not the container itself.
Podman does not have a daemon, so with podman each container has to be started as a separate systemd unit and in that case the systemd limits should apply.
Or there is another option, that you have systemd running inside the container. Which is tricky to set up, but doable. But than it has nothing to do with the fact it's a container (and not a VM).
-
@Tsaukpaetra said in WTF Bites:
You can configure it with
StartLimitIntervalSecandStartLimitBurst, but if you forget it, no rate limiting for you.I almost want to know the rationale for not including sane defaults of non-zero values, but then this is Docker we're talking about.
We can't be, because
StartLimitIntervalSecandStartLimitBurstare systemd parameters. Docker does not have them.…
s/Docker/systemd/ then.
-
TFW you really really really could use TextWatcher for something else than "save in VM" but Android devs in their infinite wisdom haven't ported that to Jetpack Compose, so you're now hand-rolling a diff algorithm to reverse-engineer which parts of text changed. Kilobyte equality comparison every frame woohoo!
-
@Tsaukpaetra said in WTF Bites:
@Tsaukpaetra said in WTF Bites:
You can configure it with
StartLimitIntervalSecandStartLimitBurst, but if you forget it, no rate limiting for you.I almost want to know the rationale for not including sane defaults of non-zero values, but then this is Docker we're talking about.
We can't be, because
StartLimitIntervalSecandStartLimitBurstare systemd parameters. Docker does not have them.…
s/Docker/systemd/ then.
Probably not.
StartLimitIntervalSecdefaults to 10s andStartLimitBurstdefaults to 5. At least on my system, but I didn't touch the default config.
-
@Tsaukpaetra said in WTF Bites:
You can configure it with
StartLimitIntervalSecandStartLimitBurst, but if you forget it, no rate limiting for you.I almost want to know the rationale for not including sane defaults of non-zero values, but then this is Docker we're talking about.
We can't be, because
StartLimitIntervalSecandStartLimitBurstare systemd parameters. Docker does not have them.…
Funny coincidence, the exact thing I was just trying to slack off from when I came to read this thread was a faulty container that crashed in the entrypoint and systemd was set to
Restart=always.
You can configure it withStartLimitIntervalSecandStartLimitBurst, but if you forget it, no rate limiting for you.Can you clarify it a bit? Systemd does not start containers, it starts services. The service might run a container, but it must do that through some tool—either docker, containerd or podman. If it does it through one of the former two, they may (don't have to, but usually do) restart the container themselves. In which case the systemd parameters only apply to start of the docker and/or containerd service and not the container itself.
I starts docker-compose. Which, when you start it directly, just returns when the entrypoint is broken in the way it was. So I'm sure it was systemd this time. Setting
Restart=no"fixed" it in that it didn't loop any more, then I had to fix the container's config of course.
-
Get ready for innovation
Finalmouse Prototype Leak Shows a Keyboard with Interactable Skins + Its Own CPU and GPU
The prototype of a Finalmouse keyboard has been leaked and it shows a keyboard with its own CPU and GPU with editable skins.
it has an internally-built GPU and CPU
ITS A BLOODY KEYBAORD GODDAMMIT!!1
-
@Applied-Mediocrity said in WTF Bites:
Get ready for innovation
Finalmouse Prototype Leak Shows a Keyboard with Interactable Skins + Its Own CPU and GPU
The prototype of a Finalmouse keyboard has been leaked and it shows a keyboard with its own CPU and GPU with editable skins.
it has an internally-built GPU and CPU
ITS A BLOODY KEYBAORD GODDAMMIT!!1
Whooow, it's own CPU! That's just like every keyboard made in the last 40 years!
-
@Applied-Mediocrity said in WTF Bites:
Get ready for innovation
Finalmouse Prototype Leak Shows a Keyboard with Interactable Skins + Its Own CPU and GPU
The prototype of a Finalmouse keyboard has been leaked and it shows a keyboard with its own CPU and GPU with editable skins.
it has an internally-built GPU and CPU
ITS A BLOODY KEYBAORD GODDAMMIT!!1
Don't worry, gamers will slurp it up.
-
@Applied-Mediocrity said in WTF Bites:
Get ready for innovation
Finalmouse Prototype Leak Shows a Keyboard with Interactable Skins + Its Own CPU and GPU
The prototype of a Finalmouse keyboard has been leaked and it shows a keyboard with its own CPU and GPU with editable skins.
it has an internally-built GPU and CPU
ITS A BLOODY KEYBAORD GODDAMMIT!!1
Don't worry, gamers will slurp it up.
We should start making a distinction between gamers and gamerphiles.
-
@Applied-Mediocrity said in WTF Bites:
Get ready for innovation
Finalmouse Prototype Leak Shows a Keyboard with Interactable Skins + Its Own CPU and GPU
The prototype of a Finalmouse keyboard has been leaked and it shows a keyboard with its own CPU and GPU with editable skins.
it has an internally-built GPU and CPU
ITS A BLOODY KEYBAORD GODDAMMIT!!1
Don't worry, gamers will slurp it up.
We should start making a distinction between gamers and gamerphiles.
Same picture. Gamers are the most gullible, stupid and dare I say retarded consumer group in existence. That includes dumb housewives and preschool kids.
-
@Tsaukpaetra said in WTF Bites:
@loopback0 said in WTF Bites:
that is, the downvotes are supposed to say boomzilla whatever the number of times the downvote count is, not any other user
The user it shows instead of the real downvoter is configurable - it's currently Mason_Wheeler but it's been others in the past.
I can't wait for it to be my turn and the dismay and chaos reigns!
You just want every post to have an upvote and a downvote from you.
-
@MrL metal hipsters and baby goths are worse.
-
-
@DogsB Let's just settle this. People suck.
-
@Applied-Mediocrity said in WTF Bites:
@DogsB Let's just settle this. People suck.
Except when you want them to.
-
Gamers are the most gullible, stupid and dare I say retarded consumer group in existence.
Nah, far from it. They only spend a couple grand a year on stupid shit. And they get the shit in return. There are people who take $20000 out of their retirement account just to give it to scammers pretending to be their own grandchildren.
-
Every market segment has its stupid quota. Like the folks with their gold plated cables that “improve quality” except they’re moving digital data around so no amount of “better conducting cable” is going to make the picture richer or the sound more dynamic.
Or the multitudinous hordes that buy kitchen gadgets they don’t need. The original Slap Chop comes to mind.
Gamers get succeeded in by a) bling of the RGB variety, b) chasing that one more FPS and c) Steam sales for games they might play eventually.
See also things like entire tiers of self help books. If a chunk of them worked, you wouldn’t need to make any more.
-
@Arantor oh, right, audiophiles. A few orders of magnitude worse than gamers, both in spending habits and in gullibility and overall stupidity. At least gamer toys work as advertised.
-
@Arantor oh, right, audiophiles. A few orders of magnitude worse than gamers, both in spending habits and in gullibility and overall stupidity. At least gamer toys work as advertised.
Most audiophile's rigs do sound a tad better than your usual Logitech or JBL speakers.
And then, there's gAmInG r00TeRz with "Triple-level Game Acceleration", 10 Gbit (yeah right) and totally not overpriced at $549.99:
ROG Rapture GT-AXE11000 | Routers | ROG United States
Tri-Band Wifi 6E Gaming Router, Latest WiFi Standard, 6GHz Band, 10 Gigabit, 2.5G Gaming Port, VPN, Network Security, Mesh WiFi System, WiFi Coverage
-
And then, there's gAmInG r00TeRz with "Triple-level Game Acceleration", 10 Gbit (yeah right) and totally not overpriced at $549.99:
To be fair, that's cheaper than the audiofool switch LTT recently looked at. Almost €800, and it's just a D-link 1Gbit switch where they slapped some Illuminati stickers on the inside.
The "triple level game acceleration" might ostensibly do something with traffic (e.g. prioritize certain packets -- whether you want that or not is a different question). But the audiophile router is guaranteed to do exactly nothing to the audio signal (which is encoded in some digital format encapsulated in multiple layers of protocols with multiple layers of error correction, and -as the video points out- maybe even encrypted. Twice.).
