h3ndrik

The answer is to create a short script that periodically queries the load, makes a decision and then triggers a reboot. Run it with a SystemD service and give it privileges to do the reboot. Useful languages for the script would be bash or python.

It's a silly way to handle it. You're probably quicker and better off solving the actual issue. Because it's not normal having this happen. Have a look at the logs, or install a monitoring software like netdata to get to the root of this. It's probably some software you installed that is looping, or having a memory leak and then swapping and hogging the IO until OOM kicks in. All of that will show up in the logs. And you'll see the memory graphs slowly rising in netdata if it's a leak.

journalctl -b -1 shows you messages from the previous boot. (To debug after you've pressed reset.) You can use a pastebin service to ask for more help if you can't make sense of the output.

Other solutions: Some server boards have dedicated hardware, a watchdog to detect something similar to that.

You can solder a microcontroller (an ESP32 with wifi) to the reset button and program that to be a watchdog.

Edit: But in my experience it's most of the times a similar amount of effort to either delve down and solve the underlying problem entirely and at once. Or writing scripts around it and putting a band-aid on it. But with that the issue is still there, and you're bound to spend additional time with it once side-effects and quirks become obvious.

And it's very centralized approach. IMHO typing in handles is a good approach for a decentralized platform. Also scanning QR codes on a conference instead of exchanging business cards. You don't need a seperate website for that. And noone wants to browse lemmyverse on a conference just to add someone (the issue they're obviously trying to solve with that.)

That article is a lot of words to say Mastodon now shows a QR code next to the handle.

It's not the first strange decision they made. I think I finally switched from Ubuntu to Debian when they introduced the Amazon advertisements to the Unity desktop. That must have been 12.10 Quantal Quetzal. I've been happy since and didn't miss the odd business strategies they pushed in the time since...

You're right. It's an oversimplification I made there. I recently tried MacOS in a VM and I talked a bit to people. You usually get a really smooth desktop experience. Apps are sandboxed, there is a fine permission system, they keep their stuff together and don't spread them across the filesystem. I think(?) the software brings their libraries along? Usually a used Macbook Pro is still fine and runs fast after 6 years. I think MacOS really shines on the desktop.

On Linux it's a bit more diverse. I mean we have the XDG specification file locations. But there's also lots of 'grown' stuff. We're still working on the sandboxing. And you get a different experience depending on the distro you're trying. And I'd prefer Linux on a server every time. It really excels for that use case and on the server we have Linux > everything else. And as a matter of fact I personally also prefer Linux on the desktop. And my Debian is also still running perfectly 6 years after I initially installed it. Had some minor issues with NVidia during the times, but that's to be expected and it wasn't that hard to fix. I wouldn't have had issues had I not mixed in testing and unstable, but there are lots of guides and tutorials around for the common woes. Which makes my argument a full circle.

Hehe, you got your answer. You're lokking at the places where 0.05% of the users are discussing their problems and some others share their crazy customizations that aren't possible with anything else. And it seems like 95% of users having issues to you.

I'd argue Linux is way more stable than Windows. If that's your perspective. (Unless you do silly stuff.) But less stable than for example MacOS. It depends on which Linux Distro we're talking about. I'd say it's MacOS > Linux > Windows. With the biggest step down from Linux to Windows.

I mean it's not only alike what you're currently using... It's the foundation of Ubuntu. Lots of packages are exactly the same.

And I think you'll find something very similar, just with the stuff missing that Ubuntu added on top, and you don't like anyways.

Hope you can move you containers and volumes without too much effort. I mean since you're starting over anyways you could also pause for a minute and think if you want to recreate something similar or switch to something different. There are other containerization techniques, podman, systemd-nspawn, you could do your server in a declarative approach with NixOS... But if you like what you have now, and don't want to learn something entirely new, I'd say Debian is probably your solution.

And I would agree. I've been using Debian on my VPS with docker-compose etc for years. Would recommend it, too. And it's pretty similar to what you have now. There isn't much needed to swich around or learn.

And it is the textbook example of a successful, community driven distro.

I'd also glue it to the back of my TV and install Kodi or Batocera on it. Next option is give it away if you don't need it. Either to someone who is still in need of a homelab or to recycling.

It can even do XMPP in addition to telephony.

And maybe clean the insides of your laptop, that's probably the first thing that could solve the issue. See if all cables are still locked in their connectors. Maybe take out the SSD, clean the contacts and you can use compressed air to clean the socket. But be careful, you want to do it right or you might cause damage. No dampness or water, it has to be either isopropyl alcohol or dry. And don't use a rag that introduces static electricity. And no workshop air compressor. Maybe something like a paintbrush is better suited. And don't just shove the vacuum in. I've done that and it might dislocate small components or key-caps and suck them in and it's a major annoyance to get them out of the vacuum cleaner bag 😆 Just be a bit careful. But I already had something like loose connectors/components cause random errors. Especially in equipment that is moved around or gets dropped occasionally. After 5 years, you might also find some dust inside. At least it used to be that way, It seems to be less of a problem with modern laptops. And more and more stuff gets soldered anyways.

And don't do too much if you're not comfortable with that. IMHO the SSD should be a safe thing to touch for most people. But it's really easy to break or bend some tiny contacts from other components or ribbon cables. And there are consumer devices that aren't really meant to be serviced. I wouldn't disassemble such a model without prior experience. If it's still working you might also leave it as is. Do backups. Storage devices often fail even without prior warning.

I'd use the built-in. Or use Oauth2 or OIDC if you want a more elaborate setup and have an application that supports it.