DigitalDilemma

Pack it into a json or CSV oneline string and shove it in a CLI password manager you can access in a scriptable way from both users. (I use the linux tool, ‘pass’ for this).

Alternatively, save it to a dropfile that only both users can access.

No idea, but ArchWiki has some of the best linux documentation around.

For a server os, do things like consider stability and ease of upgrading between major versions.

Debian does both of those things extremely well.

If you’re playing around with changing distros and your data is valuable, I’d try and find somewhere to back it up to, myself.

Ok - and what sort of cpu load do they have?

htop will also show the cpu bars and the breakdown of that - whether it’s pure cpu or iowait, which is when the cpu can’t do anything because it’s waiting on disk or network.

And how’s your memory usage looking?

I’m guessing you’ve already turned it off and on again. If not, seriously, do that. It works more time than it doesn’t for random weirdness.

Run ‘htop’ and sort by CPU (it’s a friendlier and better version of ‘top’. That’ll show you what processes are using the most CPU

Whilst you’re in there, check the free memory. If that’s low, or swap usage is high, then use htop to sort by memory usage to find what’s using the most.

If you see processes you don’t recognise, hit google and find out why. It’s very unlikely they’re malicious, but it’s far less common on linux than Windows to have random processes doing unknown stuff. If it’s using a lot of cpu or memory, there’ll be a reason. It might be a dumb reason, but you will be able to find it out.

And then when you know what the guilty process is, if it is that, and it’s not critical - you can stop it with systemctl and narrow down what’s afoot.

They’re often having to juggle with very low budgets, old equipment, low skill and zero support. And that’s before you add children…

I don’t doubt they jumped at the chance of someone helping out.

You’re talking as if “The linux community” was one single bunch of people.

Reddit isn’t Linux HQ and nor is Lemmy, nor is Facebook. #linux still active on IRC too, but not there either.

Recent convert to immich and hugely impressed by the software and project - one of FOSS’s shining stars. Good work everyone.

Others have answered why this isn’t a memory leak as such and is not as big a deal as you may think.

But if you are still concerned, you can reduce it, even if doing so is a bad idea.

1. You’re running it natively which means you’re probably using a systemd .service file to manage jackett. Research the .system setting “RuntimeMaxSec” - that will force a restart of the service every N seconds and prevent it growing. (This is a bad idea, but if you want to boss it around, you can)

2. Run it in docker and force a max memory setting. Docker will prevent it using more than you set. You can also restrict cpu usage this way too. docker-compose example goes something like:

deploy: resources: limits: cpus: 0.5 memory: 100m

Same. Been using debian stable for over two decades. It does everything I need,

At work we use EL distros in vms. All of them are backed up by image every 3 hours, so a non-booting system is generally best dealt with by simply restoring the whole vm from before the change.

I’m not opposed to atomics, but I don’t have the need and haven’t yet invested much time into learning their differences.

And you needed to find out the scanlines of your monitor before X would even display anything, and then that was a black and white grid. Then you needed to spent another day or two getting a window manager working.

Absolutely.

These services are also used by many governments around the world and considered critical infrastructure.

Terrifying, right?

Canonical is UK based, so scrub that.

But Redhat, Rocky, Alma are all owned by US legal entities and can absolutely be legally forced to do as you describe.

Technically blocked is something else, mind. We’re clever, resourceful and motivated people and US laws wouldn’t directly affect us.

However - you’re thinking small. US influence of IT is massive. Routers, servers, hardware of all levels. The most enterprise level software is US led. All of these things can be restricted, or tarriffed heavily, or sanctioned entirely. If the US wants to hurt the rest of the world, it just has to tell Broadcom to turn off vmware outside of America. Ditto Cisco, Ditto Dell, Ditto… etc etc. Sure, it would be illegal, but does the American government care about that?

Anyone telling you that “Y won’t happen because it’s unthinkable” clearly hasn’t been paying attention this year.

Debian stable is as hassle-free as you’ll get.

It sounds like your issue is more with having to migrate to a new laptop. Firstly - buy laptops that are more linux compatible and you’ll have fewer niggles like with sound, suspend and drivers.

Secondly - use “dpkg --get-selections” and “–set-selections” to transfer your list of installed software across to your new laptop. Combined with transferring your /home directory, user migration can be speeded up.

I think you make a good point, but it’s one that affects any anti-malicious protection. How do you know that the anti-virus warning you get on Windows is legitimate and not a false alert? Or that the Apparmor block wasn’t a misfire? Selinux is no better nor worse in principle than those.

In all cases, you need to stop and figure out what’s actually going on. That’s one benefit of all these things - they make you pause and, hopefully, think, when something is outside the norm.

And yep, they can be bypassed and they need to be able to be bypassed. If someone is lazy or not knowledgeable enough to make the right decision, or even just in a hurry, then they are at risk. No automated system can protect entirely against that.

Permissive mode, and yes, you absolutely can. That shows warnings but doesn’t actively block. But you still benefit from running setroubleshoot to actually figure out what and why it’s blocked something, and how to mitigate that.

Permissive is also good in that you can get a bunch of blocks reported at once, instead of having to step through one at a time, which can be useful.

I have a saying, “If it’s not DNS, then it’s Selinux”. It blocks stuff so frequently it’s a major time sink for us.

It is overly complex and difficult to understand, especially if you’re developing and deploying software that does not have correct pre-rolled policies. A regular job for me is to help developers solve this - which generally means running their service, seeing what Selinux blocks on, and then applying a fix. Repeat 2-8 times until every way Selinux is trying to access a file is explicitly allowed. And sometimes, even software that comes via official repos has buggy selinux policies that break things.

Fortunately, there are tools to help you. Install setroubleshooter amd when something doesn’t work, “grep seal /var/log/messages” and if it’s selinux causing the problem, you’ll find instructions showing you what went wrong and how to create an exception. I absolutely consider this tool essential when using any system with selinux enabled.

Fair point about systemd, or any of the other core components - I don’t know.

But I don’t think we’d be fucked - we’re ingenious and motivated and have a proven record of adapting and innovating to solve problems that stop us playing with our toys.

We’re an ingenious and motivated bunch (See all the Redhat attempts to stop clones, and lots of other examples), so yes, I think we’d absolutely work around the problem if it was to happen.

Point? I was replying about Mint and Ubuntu - what has Fedora got to do with them?