| 17 Feb 2025 |
 SigmaSquadron | Hi folks. I'm trying to use the PublicKeyFile setting in systemd.network.netdevs.<name>.wireguardPeers, as described in the manual page, but the module system keeps saying that's an invalid option. | 21:43:57 |
| SigmaSquadron | If I understood the module correctly, I think this has to be added manually in line 439-440 in nixos/modules/system/boot/networkd.nix? | 21:46:26 |
 m1cr0man | In reply to @arianvp:matrix.org
why doesn’t that get handled by the systemd-nspawn@ unit already The main problem is imperative containers rather than declarative ones. Since we're creating units ad hoc, we need to prevent the imperative ones getting stopped during config switch | 21:50:05 |
| SigmaSquadron | In reply to @sigmasquadron:matrix.org
If I understood the module correctly, I think this has to be added manually in line 439-440 in nixos/modules/system/boot/networkd.nix? if it is just that easy, i've opened https://github.com/nixos/nixpkgs/pull/382953 | 21:57:31 |
| 18 Feb 2025 |
 ElvishJerricco | ugh, this is why I really dislike how we type check networkd configs | 00:05:44 |
| ElvishJerricco | we really need a tool in upstream systemd for checking the validity of networkd files | 00:06:00 |
 Arian | I still have an experiment lying around for using systemd-analyze verify on systemd units at build time | 11:40:04 |
|  @stites:matrix.org left the room. | 12:54:41 |
 @denkn:denkn.at | Somebody know, if it is possible for services, which are oneshot to use sd_notify? Or it is more useful to set Type=notify, als if it is only a short running process, like started by a timer? | 15:09:04 |
 gdamjan | oneshot services are considered started/activated only when the process ends. so not sure if sd_notify makes sense for them | 15:18:28 |
| gdamjan | what's your use-case? | 15:18:32 |
| @denkn:denkn.at | It is a long-running process and it would be nice to check the progress. Logging would be an option, but it is only noisy, nobody needs it later. | 20:25:11 |
| @denkn:denkn.at | Eg backups. | 20:25:25 |
| Arian | Just make it Type=notify if it's long-lived | 20:26:36 |
| gdamjan | but then you'd … either loose ordering on the service, or risk the job timeout (ie how long systemd waits for a service to activate) | 23:22:30 |
| Arian | No you don't. Ordering works with Type=notify | 23:24:16 |
| Arian | Though the ordering will happen after The ready notification of course | 23:24:57 |
| gdamjan | that's what I meant | 23:51:55 |
| 19 Feb 2025 |
| ElvishJerricco | I wonder how hard it would be to do to systemd what we did to nix 2.26 and componentize the build | 06:17:06 |
| ElvishJerricco | we might be able to rid ourselves of an awful lot of the superfluous systemd dependencies in nixpkgs if we could do that. | 06:17:52 |
| Arian | We had multiple outputs build before | 07:36:34 |
| Arian | Biggest problem is sd-path.h which i still dont understand why it was added. Pointless complexity that isn't used internally | 07:37:06 |
| Arian | It causes a cyclic dependency between libsystemd and libsystemd-shared and libsystemd-core and cyclic dependency between libsystemd and some binaries iirc | 07:37:43 |
| Arian | Basically turns it into one big mess. I don't understand why we have cycle detection in multiple output derivations though. Robert told me they might remove that feature from nix. But it never happened | 07:38:18 |
| Arian | So yeh if we want it we need to either make nix support cyclic outputs (which should be fine from correctness standpoint I think?) or we need to **heavily** patch systemd | 07:38:49 |
| Arian | * So yeh if we want it we need to either make nix support cyclic outputs (which should be fine from correctness standpoint I think?) or we need to **heavily** patch systemd | 07:39:16 |
| Arian | * We had multiple outputs build before but it broke with the introduction of sd-path | 07:39:40 |
| Arian | Ah but nix is multiple derivations? In that case heavy patching is the only solution. To get rid of the cycles between all of systemd's components | 07:40:36 |
| ElvishJerricco | In reply to @arianvp:matrix.org
Ah but nix is multiple derivations? In that case heavy patching is the only solution. To get rid of the cycles between all of systemd's components If we can do it in a way that seems like a benefit to upstream, then this isn't a problem | 09:28:23 |
| ElvishJerricco | I'd have to understand that cyclic dependency better | 09:29:13 |
