Re: [systemd-devel] Setting up a VPN daemon as a Portable Service

2022-10-07 Thread David Anderson
Yeah, so far we (tailscale) haven't found a good way to run on the Steam Deck at bootup, and also survive the A/B OS updates. Systemd system extensions _can_ be activated during bootup, if you place the extension in one of the well-known locations (/var/lib/extensions would be the one to use on

Re: [systemd-devel] High CPU utilization by systemd process || Debian 8

2019-12-11 Thread David Anderson
Note that Debian 8 is very old. It runs systemd v215, which came out in 2014. So, from upstream's perspective, unless it's a well-known bug, the answer is probably "who knows? Use a more recent systemd." I suggest filing a bug with Debian and asking them for help. Debian 8 is still supported for

Re: [systemd-devel] When will my timer next run?

2019-08-30 Thread David Anderson
Did you `systemctl enable rsync-Saruman.timer` to activate the timer? Timers can be enabled and disabled just like services, you need to enable it after creating. - Dave On Fri, Aug 30, 2019 at 8:05 PM Kenneth Porter wrote: > I've created my service timer with the following: > > [Timer] > #

Re: [systemd-devel] connection failure

2019-07-02 Thread David Anderson
Hi! This is the wrong list for your question. You should ask this on the help list for your linux distro, it looks like they've configured Docker incorrectly, or there's some extra required setup that you're missing. You can also consult `journalctl -u docker.service` to find clues on why Docker

Re: [systemd-devel] Multiple initrds in unified kernel images?

2018-10-05 Thread David Anderson
uld just work. Please let me know if I'm wrong, and otherwise - thanks for being my rubber ducks! - Dave On Fri, Oct 5, 2018 at 12:02 AM David Anderson wrote: > Hi, > > I'm exploring systemd-boot and secure booting for an Arch Linux install. > To get secure boot working right,

[systemd-devel] Multiple initrds in unified kernel images?

2018-10-05 Thread David Anderson
Hi, I'm exploring systemd-boot and secure booting for an Arch Linux install. To get secure boot working right, I need to build a unified kernel image that I can sign. However, I also need to pass 2 initrd images into the boot process (one for CPU microcode, and the proper OS iniramfs). But,

[systemd-devel] udev failing to assign consistent biosdevnames to my ethernet interfaces

2014-01-26 Thread David Anderson
This is a continuation of a discussion I had on #systemd. I have a server that has two onboard ethernet chipsets, and a fresh Arch linux install (systemd/udevd v208). On this system, consistent interface naming fails, and I end up with eno1 and eth1 after bootup. The full boot log is at

Re: [systemd-devel] udev failing to assign consistent biosdevnames to my ethernet interfaces

2014-01-26 Thread David Anderson
On Mon, Jan 27, 2014 at 5:18 AM, Andrey Borzenkov arvidj...@gmail.comwrote: В Mon, 27 Jan 2014 04:18:20 + David Anderson d...@natulte.net пишет: This is a continuation of a discussion I had on #systemd. I have a server that has two onboard ethernet chipsets, and a fresh Arch linux