On Tue, Feb 14, 2023 at 5:31 PM Thomas Köller wrote:
>
> I cannot start the 'ssh' command from a systemd service. A very simple
> service file demonstrates the problem:
Your test service works fine for me on Gentoo Linux.
I would guess execution is being blocked by something like AppArmor or SEL
🎆 A new, official systemd release has just 🎉 been 🎊 tagged 🍾. Please download
the tarball here:
https://github.com/systemd/systemd/archive/v253.tar.gz
Changes since the previous release:
Announcements of Future Feature Removals and Incompatible Changes:
* We intend to r
I'be been having issues lately trying to automatically remount an external
USB drive that is mounted at boot from an fstab entry:
LABEL=data-ssd /opt/data-ssd ext4 defaults,nofail,users 0 2
I'm using systemd 244 and after some investigation I learned about the
possibility to launch a systemd
> On 15 Feb 2023, at 10:31, Aditya Sharma wrote:
>
> Hi Kevin,
>
> When the TTLs expire, those records in the cache become 'stale', and are
> normally purged. Your request is to have an option in systemd-resolved to
> *not* purge those records, but to continue serving them in case it is unab
On Wed, Feb 15, 2023, at 05:31, Aditya Sharma wrote:
> We were thinking of an approach where we keep on serving the last known good
> FQDNs even after the TTL has expired (only when we are unable to communicate
> with the resolvers). For that, we need to intercept the DNS calls and
> maintain so
Hi Kevin,
*When the TTLs expire, those records in the cache become 'stale', and are
normally purged. Your request is to have an option in systemd-resolved to
*not* purge those records, but to continue serving them in case it is
unable to communicate with the configured recursive resolver(s).*
Sor
