Hi, I was looking into a way of having Weston signal when it is available for clients to connect, and using systemd seems like a good way to achieve this.
The idea here is to have Weston inform SystemD that it is ready, by calling sd_notify() just before entering the main loop. SystemD expects the signal to come from the process it fork'd, so there's a new opcode added to weston-launch for it to relay the notify message from Weston. I'm not really sure about this approach though. I'm also not sure about the implications of just clearing the environment for the child process. It seems like this would be fine for me, but maybe I'm missing something. And perhaps the patches should be squashed. Thanks, Ander Ander Conselvan de Oliveira (2): compositor: Add systemd notification support weston-launch: Only clear the environment of the child process configure.ac | 6 ++++++ src/Makefile.am | 10 ++++++---- src/compositor.c | 38 ++++++++++++++++++++++++++++++++++++++ src/weston-launch.c | 35 +++++++++++++++++++++++++++-------- src/weston-launch.h | 3 ++- 5 files changed, 79 insertions(+), 13 deletions(-) -- 1.7.10.4 _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
