Control: severity -1 normal On 10/09/2020 15:39, 積丹尼 Dan Jacobson wrote: > Bug still affecting several of my machines. Forwarding to > https://github.com/systemd/systemd/issues/17004 .
I don't know why you think this bug is 'grave'. This does not make your system unusable (and you've found a workaround), does not cause data loss, and is not a security hole. The fact is that ppp is very old software and nobody ever thought about things like systemd-resolved even existing when the scripts around it were written. I believe that, as ppp assumes resolvconf, it should be systemd-resolved's responsibility to configure itself with DNS servers from PPP. Consequently I will update the 0000usepeerdns script to exit early (taking no action) if systemd-resolved is running. I'm open to working with the systemd maintainers to improve on this, though. For reference, resolvconf does this using: https://sources.debian.org/src/resolvconf/1.84/debian/resolvconf.000resolvconf.ppp.ip-up/ In my opinion the most sensible way to run pppd these days is through some kind of abstraction layer such as NetworkManager. Regards, Chris -- Chris Boot bo...@boo.tc
