That would make sense if they ran servers on non-LTS release. Do they do that?
avidamoeba
joined 1 year ago
This is why I'm no longer upgrading to non-LTS releases. They add the new stuff in those, the good souls that use them test it and by the time it gets to the LTS, things generally work fine. I think PipeWire will replace PulseAudio in 24.04. It's had a good run while it lasted. 15 years of mainstream use. βΊοΈπ
Well the PulseEffects version is still alive and well in Ubuntu's repos and it will be for a while.
Anytime you're asking this, go for the projects Quick Start / Getting Started doc. In this case here. If you're on a Debian based system Prometheus is already packaged in the repository so you don't have to download the latest. You likely won't win anything but the pain for having to set up the bare binary as a service with systemd. I followed that doc to setup mine but installed it from apt.
On a second thought, if you're getting it from the repo and it already has a systemd unit defined, it might be more difficult to follow the Getting Started doc. You know what, follow it as-is. Once you have something running and monitoring ad-hoc, it'll be easy to install from apt and put your config in it.
I think Prometheus is a good industry standard. It can do everything you listed except for restarting stuff. It's got a decent built-in monitoring capability and you can extend it trivially to monitor anything. For example I wrote a 5-liner to monitor ZFS health and another for LVM. I even monitor my routers with it. OpenWrt has an installable node exporter for Prometheus.
Service restarting is a remote execution capability and generally falls outside of the monitoring domain. You'd be better off implementing that with another process/service manager. If you're running systemd, that's one of its primary purposes. You can use it to start/stop/restart containers just like normal processes.
I call the 10-feet-pole on this one.
This peertube.social doesn't lead me to where I thought it would. π
Try to get Dolphin/KDE to remember the credentials. I know GNOME can do it so I assume it's possible in KDE.
Dolphin is your file explorer program. That's part of the KDE desktop app collection. It allows you to connect to a samba share. In the background it mounts the samba share to a your local filesystem. The mount point is a location, it looks like a folder but it's actually a view into the samba share. This mounting is done by the kernel using a filesystem driver which talks to the samba server. In order for the driver to do this, it needs your samba credentials. Dolphin presents some UI for you to input them and it passes them to the driver. If it asks for them every time, it means that it doesn't remember them, or if it depends on something else to remember them, it's not working. There might be a way in KDE to tell it to remember the credentials. I'm not a KDE user or expert.
If you can't do that, you could do what Dolphin does by yourself. You could tell the driver the same information Dolphin does but you can also store the credentials in a file and have it read those from there. This can be done in multiple ways. Via fstab, systemd, command line, and possibly many more.
Sounds like a KDE thing where it doesn't remember your credentials/doesn't want to automatically provide them to the connector. You could take over the fs mounting and do it via systems or some other means if there's no way for KDE to do it.
Weird, the link goes to Lemmy's page for me - https://liberapay.com/Lemmy. Did OP have it wrong and then updated it?
Well this change can't improve anything about Power Saver. It only affects Balanced which now should be a bit less of a gas guzzler.
And yes, even the most aggressive power saving we have at the moment isn't anything to write home about. If we paid 10 developers to hunt down power drain issues and submit fixes for a few years we may get closer to macOS. π