On Wed, 11.02.15 22:28, Keller, Jacob E (jacob.e.kel...@intel.com) wrote: > On Wed, 2015-02-11 at 21:46 +0100, Lennart Poettering wrote: > > On Wed, 11.02.15 20:36, Keller, Jacob E (jacob.e.kel...@intel.com) wrote: > > > > > > > Yes. I believe that possibly the netlink messages are occurring too > > > > > early before networkd has started. Thus, when I restart the service > > > > > after startup it works fine. > > > > > > > > Well, the first thing after subscribing to links coming/going that > > > > networkd does is query the kernel for the list of devices it has. This > > > > means that it should always get all links, regardless when it is > > > > started. > > > > > > What about network device renames? Devices are renamed after they > > > appear. Is it also possible that networkd is started too early and thus > > > the devices haven't actually appeared yet? But.. then it should get the > > > message once it does appear? (assuming here that it continues listening > > > to rtnl messages about links) > > > > networkd should get all netlink msgs about all of this just fine, and > > be able to track renames and everything. > > > > > How difficult would it be to create an RPM? > > > > Well, you can get the spec file from fedpkg and then use it on a > > tarball from systemd git made with "make dist". But you probably need > > to make a number of updates to the .spec file. Unless you are an RPM > > guru I wouldn't bother. > > > > Lennart > > > > Ok. I got the upstream systemd installed. Now I get a very different > behavior, which I am unsure of. > > I cut off the last message as it repeated some odd ten thousand times or > so... Presumably retry/failing... > > At any rate, it appears possible that some configuration is wrong, or > similar? Any suggestions/thoughts now? > > Feb 11 14:21:47 jekeller-copperpass systemd-networkd[1068]: enp4s0f0 : > flags change: +UP > Feb 11 14:21:47 jekeller-copperpass systemd-networkd[1068]: enp4s0f0 : > enp4s0f0 : could not bring up interface: Invalid argument
OK so this is already weird. > Feb 11 14:21:52 jekeller-copperpass systemd-networkd[1068]: DHCP CLIENT > (0xc7096673): could not receive message from raw socket: Invalid argument Hmm, this one might actually be caused by d6d810fbf8071f8510450dbacd1d083f37603656. WIll revert that, please retest then! Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
