No description
Find a file
Simon Ser 392da918e6 build: fix logind feature summary when auto-detected
If -Dlogind=auto but systemd/elogind isn't available,
logind_provider would get set to the last item of the foreach loop.
This would incorrectly report "systemd: YES".
2021-04-08 23:07:35 +02:00
.builds ci: Use 'auto' for arch linux logind 2021-04-08 23:07:35 +02:00
common Normalize log texts a bit 2021-03-02 00:27:38 +01:00
contrib/systemd contrib: Add Documentation to systemd unit 2021-03-16 14:27:45 +01:00
examples/simpletest simpletest: Close fd after closing device 2020-12-14 23:41:17 +01:00
include Add no-op session 2021-03-26 11:11:26 +01:00
libseat Avoid a clang-format quirk 2021-03-26 11:34:13 +01:00
man man: Mention assistance from other contributors 2020-09-07 23:54:52 +02:00
seatd client: enable cr_pid on FreeBSD >= 12.3 2021-03-21 16:27:21 +01:00
tests connection: Add unittest 2020-10-12 18:02:00 +02:00
.clang-format Add clang format specification 2020-07-31 00:23:03 +02:00
LICENSE Add LICENSE 2020-07-31 01:34:04 +02:00
meson.build build: fix logind feature summary when auto-detected 2021-04-08 23:07:35 +02:00
meson_options.txt build: add explicit logind provider option, auto-detect by default 2021-04-08 23:07:35 +02:00
README.md readme: Remove alpha label 2021-03-18 15:45:40 +01:00

seatd and libseat

A minimal seat management daemon, and a universal seat management library.

Currently supports Linux and FreeBSD.

What is seat management?

Seat management takes care of mediating access to shared devices (graphics, input), without requiring the applications needing access to be root.

What's in the box?

seatd

A seat management daemon, that does everything it needs to do. Nothing more, nothing less. Depends only on libc.

libseat

A seat management library allowing applications to use whatever seat management is available.

Supports:

  • seatd
  • (e)logind
  • embedded seatd for standalone operation

Each backend can be compile-time included and is runtime auto-detected or manually selected with the LIBSEAT_BACKEND environment variable.

Which backend is in use is transparent to the application, providing a simple common interface.

Why not (e)logind?

systemd-logind is not portable, and being part of the systemd project, it cannot be used in an environment not based on systemd. Furthermore, "simple" is definitely not within the set of adjectives that can be used to describe logind. For those in the dark, take a glance at its API. Plus, competition is healthy.

elogind tries to isolate systemd-logind form systemd through brute-force. This requires actively fighting against upstream design decisions for deep integration, and the efforts must be repeated every time one syncs with upstream. And even after all this work, one is left with nothing but a hackjob.

Why spend time isolating logind and keeping up with upstream when we could instead create something better with less work?

Why does libseat support (e)logind?

In order to not be part of the problem. We will not displace systemd-logind anytime soon, so for user shells like sway, seatd joins the ranks of logind and direct session management for things they need to support.

Instead of giving user shell developers more work, libseat aims to make supporting seatd less work than what they're currently implementing. This is done by taking care of all the seat management needs with multiple backends, providing not only seatd support, but replacing the existing logind and direct seat management implementations.

I want more

Go to #kennylevinsen @ chat.freenode.net to discuss, or use ~kennylevinsen/seatd-devel@lists.sr.ht.