Re: [systemd-devel] Portable service binding a system port

2020-04-08 Thread François
Hi, Lennart, thanks a lot for your time and answer. > Le 31 mars 2020 à 15:19, Lennart Poettering a écrit : > > Ideally unbound would support socket activation, so that PID 1 can > bind the socket and pass it in pre-bound. Noted. I’ll give this a try as an exercise and see how it goes :) >

Re: [systemd-devel] Portable service binding a system port

2020-03-31 Thread Lennart Poettering
On Fr, 07.02.20 11:05, François (francois+syst...@kubler.org) wrote: > Hi, > > I’m finally answering my own question - well at least partially. > > I managed to identify the culprit : the `PrivateUsers=yes` directive. > > If I override it with a drop-in and set it to `no`, it works as expected

Re: [systemd-devel] Portable service binding a system port

2020-02-07 Thread François
Hi, I’m finally answering my own question - well at least partially. I managed to identify the culprit : the `PrivateUsers=yes` directive. If I override it with a drop-in and set it to `no`, it works as expected and I can successfully bind to port 53. But I still don’t understand why,

[systemd-devel] Portable service binding a system port

2020-01-23 Thread François
Hi, I’m playing around with portables services and I’m trying to make unbound (the DNS resolver) work. Despite all my efforts these last days and some Google-Fu, I can’t make it work. It always fails when trying to bind the interface on port 53, with a « permission denied » message. The exact