Hello Mantas.
You was right, the logic of my code kept itself away from accepting a
connection, when working with the control socket passed by the systemd.
I hardcoded accept() function and this worked out - a command was read.
Thanks for your attention!
чт, 27 июн. 2019 г. в 13:44, Mantas Mikulėn
Hi all,
I'm trying to process the `sd_bus_error` set in a `sd_bus_message_handler_t`
callback in my main loop but I can't seem to be able to do it properly...
Here is what I tried:
- In the callback I tried setting the error using `sd_bus_reply_method_error`
and `sd_bus_error_set`
- In the ma
On Thu, Jun 27, 2019 at 1:29 PM Donat Zenichev
wrote:
> Hi systemd community.
> Recently I've come accross one interesting problem with API of systemd.
> The problem is that, I'm not able to read commands comming to the AF_UNIX
> socket, that was created by systemd and passed to my program using
Hi systemd community.
Recently I've come accross one interesting problem with API of systemd.
The problem is that, I'm not able to read commands comming to the AF_UNIX
socket, that was created by systemd and passed to my program using
sd_listen_fds(0) function.
What actually program requires, is A
