Am 07.10.2014 um 15:16 schrieb martin f krafft: > also sprach Michael Biebl <[email protected]> [2014-10-07 15:12 +0200]:
>> It warns you, that the default systemd-networkd configuration >> makes use of the new interface naming, but that it is not enabled. >> Keep in mind, that this message is logged by systemd-udevd, not >> systemd-networkd itself. So you get that irregardless whether >> systemd-networkd is enabled/active or not. > > What is the rationale for this choice? Why did you guys decide it > was best to log a warning every few seconds and require the admin to > take action to restore the old behaviour? You have that backwards. We made the new interface naming opt in to keep the old behaviour, simply because we didn't want to deal with that transition at this time. The log message is not by "us guys", but, as I explained, the result of upstream using a different default value, and because of that, udevd warning about this fact. Now, I don't get this log message every second as you say. But only during boot when the network interfaces are detected. In my case 3 interfaces, so 3 log messages during boot and that's about it. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
