On Fri, Aug 18, 2023 at 12:22 AM Simon Ser <contact@emersion.fr> wrote:
>
> systemd integration was already discussed here:
> https://lists.sr.ht/~kennylevinsen/seatd-devel/%3C20230127104421.4075465-1-m.tretter%40pengutronix.de%3E

Well that's systemd socket activation while this is systemd notify support.

It appears that there's some desire to avoid linking with libsystemd just
for the sake of not linking with libsystemd, even though doing so would
result in a much better integration.

>
> I would personally prefer not to have any systemd-specific stuff inside
> seatd, only service manager independent logic, wired up to systemd in

This lets systemd know when the service is ready and informs systemd
of any errors that occur.

Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
---
 contrib/systemd/seatd.service |  2 +-
 meson.build                   | 12 ++++-
 meson_options.txt             |  1 +
 seatd/seatd.c                 | 86 +++++++++++++++++++++++++++++++++++
 4 files changed, 99 insertions(+), 2 deletions(-)

diff --git a/contrib/systemd/seatd.service b/contrib/systemd/seatd.service
index bbbaf23..e7f9ca3 100644
--- a/contrib/systemd/seatd.service
[message trimmed]