I'm currently working with a client that needs LinkLocalAddressing as a
fallback when DHCP resolution fails. Currently with systemd-networkd it
looks like you have both DHCP and LinkLocalAddressing on, but that means
you get a second 169.254.*.* address even when DHCP succeeds. We
investigated usin
On Di, 17.07.18 09:25, Martin Häcker ([email protected]) wrote:
> On 13.07.18 17:07, Lennart Poettering wrote:
> > journald is designed to just write out what is being thrown at it,
> > with the speed the underlying device permits. It is using relatively
> > large reception buffers for this
On 13.07.18 17:07, Lennart Poettering wrote:
> journald is designed to just write out what is being thrown at it,
> with the speed the underlying device permits. It is using relatively
> large reception buffers for this, so that clients don't have to stall
> on journald. If you flood journald heavi
