[systemd-devel] journald fsync() errors

[vcaputo]

Back when I worked on making fsync() in journald asynchronous, I
preserved the existing strategy of ignoring fsync() errors.

In reading [1], I am reminded of this situation and am again wondering
why this is the case.  Shouldn't journald trigger a journal rotate when
fsync() realizes an IO error, marking the previous journal as corrupt?

Can someone remind me of the rationale behind the existing approach?

Regards,
Vito Caputo

[1] 
https://www.postgresql.org/message-id/flat/CAMsr%2BYE5Gs9iPqw2mQ6OHt1aC5Qk5EuBFCyG%2BvzHun1EqMxyQg%40mail.gmail.com
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] nspawn: how to rename network interfaces?

[Matthias Pfau]

Hi there,
I just tried to rename ipvlan and macvlan devices in a container with 
systemd.link. This does not seem to work with debian stretch (host and 
container).

Is it possible to rename ipvlan and macvlan devices in a container? If not: Is 
there another way to define custom interface names?

Thanks!

Cheers,Matthias Pfau
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel