I went to sleep last night after posting this and left a ssh connection open to see what it did in the morning when I woke up. And when I woke up and checked it out, I found that coincidentally it stopped doing the timer almost exactly as I went to sleep, yet I don’t think I was doing anything that would make that happen. I have no idea why it stopped, but it hasn’t started again either.
I was running the same things I always have, which is just a large collection of services in docker. I went to sleep last night after posting this and left a ssh connection open to see what it did in the morning when I woke up. And when I woke up and checked it out, I found that coincidentally it stopped doing the timer almost exactly as I went to sleep, yet I don’t think I was doing anything that would make that happen. I have no idea why it stopped, but it hasn’t started again either.
I have no idea when it started, I just happened to notice it last night. I went to sleep after posting this and left a ssh connection open to see what it did in the morning when I woke up. And when I woke up and checked it out, I found that coincidentally it stopped doing the timer almost exactly as I went to sleep, yet I don’t think I was doing anything that would make that happen. I have no idea why it stopped, but it hasn’t started again either.
I went to sleep last night after posting this and left a ssh connection open to see what it did in the morning when I woke up. And when I woke up and checked it out, I found that coincidentally it stopped doing the timer almost exactly as I went to sleep, yet I don’t think I was doing anything that would make that happen. I have no idea why it stopped, but it hasn’t started again either.
I just reduced my global max connection from infinity to 500 (somehow that increased my upload speed?) and it reduced qbits shit by a couple thousand, but it’s still in the many thousands. I’m assuming the number on the left is literally just how many files it’s using, in which case, how could that ever get below 1024? Not to mention I have many other services that are also above 1024. (See below). In any case, I’m only using 14 GB of memory out of my 32 GB of ram and 16 swap, so I think it would be fine to increase the limit, but that does worry me a bit.
18841 python3
16294 qbittorre
14064 docker-pr
11900 Sonarr
8940 Radarr
8441 Cleanupar
8246 Prowlarr
6130 java
5836 postgres
3532 container
2766 gunicorn
1980 dockerd
lol! You’re totally right
running this, i find that qbittorrent fluctuates around 19000 and python3 is steady around 18000, and my arrs a bit behind, in this case, I’m not sure if there’s anything I can easily do without stopping seeding
18460 qbittorre
18424 python3
14056 docker-pr
11424 Sonarr
11072 Radarr
9440 Prowlarr
I’d creamy your jalapeño sauce… ;3
This is indeed with network manager. I experimented with just barebones iwd but I couldn’t get it to work
I’m not 100% sure if this is the case, as I haven’t set up a server for it yet. But it seems like that pricing is mostly just for the official fluxer server? I’d be willing to bet that it really just depends on what the server admin configures
yt-dlp is great for cli, and if you want a web gui, you can run metube in docker
interesting! I’ve never seen that before, maybe it would, maybe it wouldn’t.
It does have screen sharing now! The Linux client currently can’t share system audio, but I think they’re working on that
58, my cpu is usually around 10-20% usage. I really don’t have any trouble managing/maintaining these. Things break almost weekly but I understand how to fix them every time, it only takes a few minutes
Interesting! I guess that makes sense.