It is asking for the same resource twice in the way I read that aren't IPv4 and IPv6 sharing socket space? that would be a resource allocation error if true right? On Dec 5, 2012 8:53 AM, "Mirco Tischler" <[email protected]> wrote:
> 2012/12/5 Thomas H.P. Andersen <[email protected]> > >> I was looking into why the unit files for talkd/ntalkd were not >> working [1]. For some reason specifying these two lines in the same >> socket file triggers an unfortunate behavior in systemd: >> ListenDatagram=[::]:517 >> ListenDatagram=0.0.0.0:517 >> >> Systemd first of all fails to start the service. It then tries >> starting it again and again repeatedly. This quickly reaches the limit >> for failing to start a service too often. It still just continues and >> it spams the journal about having hit this limit. It caused a >> noticeable slow down of the computer and my log file began rotating. >> >> I have not looked into what is going on in systemd, or whether this is >> a bug or not. However it is case where I think that it could be nice >> to provide a clear error message. >> >> Maybe someone can spread some light about what is going on here? A >> socket file with just one of the two ListenDatagram-lines works just >> fine. >> >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=737219 > > > My guess is systemd gets confused because the two addresses overlap. By > default specifying an ipv6 address will make the service available on both > ipv6 and ipv4, so the second directive is redundant. This can be disabled > with BindIPv6Only=ipv6-only. But systemd could indeed behave nicer in this > situation :) > > Mirco > > _______________________________________________ > systemd-devel mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/systemd-devel > >
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
