Re: [systemd-devel] [Libguestfs] [libnbd PATCH v3 19/19] socket activation: set LISTEN_FDNAMES

2023-03-24 Thread Laszlo Ersek
On 3/24/23 15:52, Eric Blake wrote: > [attempting to loop in systemd folks; this started in libnbd at > https://listman.redhat.com/archives/libguestfs/2023-March/031178.html > - although I may have to retry since I'm not a usual subscriber of > systemd-devel] > > On Fri, Mar 24, 2023 at

Re: [systemd-devel] [Libguestfs] [libnbd PATCH v3 19/19] socket activation: set LISTEN_FDNAMES

2023-03-24 Thread Laszlo Ersek
On 3/24/23 15:52, Eric Blake wrote: > [attempting to loop in systemd folks; this started in libnbd at > https://listman.redhat.com/archives/libguestfs/2023-March/031178.html > - although I may have to retry since I'm not a usual subscriber of > systemd-devel] > > On Fri, Mar 24, 2023 at

Re: [systemd-devel] Cannot mount /sys/kernel/debug in nspawn container

2023-03-24 Thread Martin
On 2023-03-24 20:01, Michal Koutný wrote: > On Sun, Mar 19, 2023 at 07:16:56PM +, Martin wrote: >> Any idea, what I might missing? > > Permissions? > (Incresing logging verbosity may give you some hints. [1][2]) Thank you very much! I'm not sure, if I will debug that, because meanwhile I

Re: [systemd-devel] coredumpctl: matching by e.g. env var?

2023-03-24 Thread Michal Koutný
On Wed, Mar 15, 2023 at 09:43:37AM +0100, Stephan Bergmann wrote: > Any thoughts? Luca's idea of temporary units may work for your runtime differentiation. Although, I was thinking of a another use of such a "tagging" mechanism -- systemd-coredump could skip processing of certain coredumps to

Re: [systemd-devel] Cannot mount /sys/kernel/debug in nspawn container

2023-03-24 Thread Michal Koutný
Hello. On Sun, Mar 19, 2023 at 07:16:56PM +, Martin wrote: > Any idea, what I might missing? Permissions? (Incresing logging verbosity may give you some hints. [1][2]) > PS: My ultimate goal is to run bpftrace in the container. Seems to be > slightly tricky. I wouldn't call it a

Re: [systemd-devel] [Libguestfs] [libnbd PATCH v3 19/19] socket activation: set LISTEN_FDNAMES

2023-03-24 Thread Eric Blake
[attempting to loop in systemd folks; this started in libnbd at https://listman.redhat.com/archives/libguestfs/2023-March/031178.html - although I may have to retry since I'm not a usual subscriber of systemd-devel] On Fri, Mar 24, 2023 at 11:32:26AM +0100, Laszlo Ersek wrote: > >> @@ -245,6

Re: [systemd-devel] systemd-resolved: performance question

2023-03-24 Thread Petr Menšík
I think it is fairly easy. If the /etc/resolv.conf changes not by a change of systemd-resolved, it is very likely the address specified in it does not point to resolved anymore. In that sense it does not matter what systemd-resolved does with such information and how quickly. Does it update

Re: [systemd-devel] systemd-resolved: performance question

2023-03-24 Thread Lennart Poettering
On Fr, 24.03.23 03:16, Petr Menšík (pemen...@redhat.com) wrote: > Even if it could not use filesystem monitoring, I guess it could check those > files only once per second or so. Should not depend on number of done > queries. It's not so easy. We generally want to give the guarantee that if

Re: [systemd-devel] CPUAffinity=all ?

2023-03-24 Thread Lennart Poettering
On Do, 23.03.23 16:59, Etienne Champetier (champetier.etie...@gmail.com) wrote: > Le jeu. 23 mars 2023 à 16:37, Etienne Champetier > a écrit : > > > > Hello, > > > > I'm setting `CPUAffinity=0-1` in /etc/systemd/system.conf, this works great. > > Now, I want one of my units to set CPUAffinity to