Re: [systemd-devel] multiple starts for a socket-based service

2023-08-04 Thread Kevin P. Fleming
On Fri, Aug 4, 2023, at 18:11, Ross Boylan wrote: > Theory: since br0 has no associated IP address when socket creation is > attempted, the socket creation fails. If so, I need to delay socket > startup until br0 has an IP4 address, but I'm not sure how to do > that--or even if that is the problem

Re: [systemd-devel] multiple starts for a socket-based service

2023-08-04 Thread Ross Boylan
Well, the problem is not completely solved. The socket is not starting when the system comes up (tried it twice): Aug 04 11:33:16 barley systemd[1757]: family.socket: Failed to create listening socket (192.168.1.10:14987): Cannot assign requested address Aug 04 11:33:16 barley systemd[1]: family.s

Re: [systemd-devel] PAMName=login, systemctl stop

2023-08-04 Thread Tomasz Pala
On 03.07.2023 14:17, Lennart Poettering wrote: > logind's session ID you'll find in the $XDG_SESSION_ID env var. > > you can use this to kill your own session: > > loginctl kill-session $XDG_SESSION_ID > > if you want to know which systemd unit your process belongs to use: > > ps --pid