Re: [systemd-devel] Anonymous SYSTEMD_NOTIFY socket

2023-06-28 Thread Lennart Poettering
On Di, 27.06.23 13:36, Adrian Vovk (adrianv...@gmail.com) wrote: > Hello! > > I'm working on passing sd_notify events from systemd-{pull,import} through > sysupdate. > > All services that consume sd_notify events (systemd itself, importd, > machined, homed, etc) act as daemons and own a directory

Re: [systemd-devel] Anonymous SYSTEMD_NOTIFY socket

2023-06-28 Thread Mantas Mikulėnas
On Tue, Jun 27, 2023 at 8:36 PM Adrian Vovk wrote: > Hello! > > I'm working on passing sd_notify events from systemd-{pull,import} through > sysupdate. > > All services that consume sd_notify events (systemd itself, importd, > machined, homed, etc) act as daemons and own a directory in /run. Thus

[systemd-devel] Anonymous SYSTEMD_NOTIFY socket

2023-06-27 Thread Adrian Vovk
Hello! I'm working on passing sd_notify events from systemd-{pull,import} through sysupdate. All services that consume sd_notify events (systemd itself, importd, machined, homed, etc) act as daemons and own a directory in /run. Thus, they can open a notification socket at, say, /run/SERVICENAME/n