| 28 Sep 2021 |
 eyJhb | If anyone can look at it, it would be great :) | 13:44:33 |
 andi- | eyJhb: I would argue that DUIDType and DIDRawData could need some input validation but I won't -1 if it doesn't get those... | 13:56:54 |
| eyJhb | andi-: it is taken from the DHCPv4 section, which has none as well :p So I think that should be a separate PR to add for both of them :) | 13:57:55 |
| andi- | The link-layer-time looks daunting to verify | 13:57:59 |
| eyJhb | andi-: does it make sense, that it should be a seperate PR? To add it for both? :) | 14:08:44 |
| andi- | Yeah if you want to tackle that. | 14:08:58 |
| andi- | I am fine with the current PR as is | 14:09:03 |
| andi- | generally I'd love if we did perform more validation on the Nix side (with escape hatches?). | 14:09:23 |
| andi- | The last thing I want is a system without network :D | 14:09:30 |
| eyJhb | I have no idea to do any validation on the DUIDType + DUIDRawData :p I might be able to look into it. But unsure how well that would go | 14:09:46 |
| eyJhb | Ohh come on, a system without networking? THat's fun! :D | 14:09:55 |
| andi- | I just realized that with v249 the systemd-wait-online program behaves different and now I had to explicitly disable DHCP/AcceptRA on a bond interface where I didn't configure anything. | 14:10:33 |
| eyJhb | I have some weird issue with a tempoary address w/ IPv6. But I am quite sure it's just my ISP screwing around.... | 14:15:36 |
| andi- | it is always your weird ISP | 14:17:22 |
| eyJhb | Well, you know first hand that my ISP is doing some weird stuff andi- :D | 14:18:06 |
|  khalil joined the room. | 15:03:13 |
 gdamjan | In reply to @andi:kack.it
I just realized that with v249 the systemd-wait-online program behaves different and now I had to explicitly disable DHCP/AcceptRA on a bond interface where I didn't configure anything. just in case you didn't know it, there's RequiredForOnline= https://www.freedesktop.org/software/systemd/man/systemd.network.html#RequiredForOnline= | 15:28:11 |
| andi- | In reply to @gdamjan:spodeli.org
just in case you didn't know it, there's RequiredForOnline= https://www.freedesktop.org/software/systemd/man/systemd.network.html#RequiredForOnline= I had that set on exactly the one interface that I care about. I did expect (from reading the changelog / manpage) that it would ignore other interfaces. | 15:29:34 |
|  ryantm joined the room. | 15:42:25 |
| gdamjan | default is yes by default | 15:43:39 |
| gdamjan | I guess wait-online might need a config file of it's own | 15:44:20 |
| andi- | nah, please don't. I think it is fine as is just that it waits for everything that has a DHCP/AcceptRA configuration is a bit weird | 19:10:05 |
| andi- | There are a few new cli options that I should explore. | 19:10:16 |
| 29 Sep 2021 |
|  eliasp joined the room. | 08:37:19 |
| 30 Sep 2021 |
|  Robby O'Connor joined the room. | 01:16:41 |
|  matrixforever joined the room. | 02:16:18 |
| matrixforever left the room. | 04:37:23 |
| Robby O'Connor left the room. | 05:49:51 |
| eyJhb | So I am trying to make Bitlbee use DynamicUser=true instead, but I am unsure which dir I should point to?
I get the following message
Sep 30 09:45:19 tutti systemd[1757215]: Found pre-existing public StateDirectory= directory /var/lib/bitlbee, migrating to /var/lib/private/bitlbee.
Sep 30 09:45:19 tutti systemd[1757215]: Apparently, service previously had DynamicUser= turned off, and has now turned it on.
But should I then point the config (bitlbee config) to /var/lib/private/bitlbee, or /var/lib/bitlbee?
From the systemd manpage I see the following Both from perspective of the host and from inside the unit, the relevant directories hence always appear directly below /var/cache, /var/log and /var/lib., which I guess means it will always create a symbolic link from /var/lib/bitlbee to /var/lib/private/bitlbee?
| 07:49:44 |
| eyJhb | Ohh ffs, I completely missed the line above it...
Symbolic links are created to hide this difference in behaviour. Both from perspective of the host and from inside the unit, the relevant directories hence always appear directly below /var/cache, /var/log and /var/lib.
| 07:50:56 |
