No description
Find a file
Kenny Levinsen 6747c5f3f8 poller: Raise signals through self-pipe
Signal handling relied on poll(2) being interrupted by signals, followed
by a check for signal handlers flagging a signal as received. This only
allowed signals that were received during poll(2) to be handled
correctly.

Implement the usual self-pipe implementation, where signal handlers
write an arbitrary byte to a polled file descriptor to ensure proper
level-triggered signal handling.
2020-09-22 01:01:46 +02:00
.builds ci: ASan smoketest on FreeBSD 2020-09-01 02:27:05 +02:00
common Remove unused list implementation 2020-08-31 14:14:39 +02:00
contrib/systemd contrib: Add example systemd service 2020-08-07 16:06:00 +02:00
examples/simpletest simpletest: Set log level to debug 2020-08-28 01:26:39 +02:00
include poller: Raise signals through self-pipe 2020-09-22 01:01:46 +02:00
libseat libseat: Handle SERVER_ERROR correctly 2020-09-07 23:35:24 +02:00
man man: Mention assistance from other contributors 2020-09-07 23:54:52 +02:00
seatd poller: Raise signals through self-pipe 2020-09-22 01:01:46 +02:00
tests test: Add test_run and test_assert macros 2020-08-31 14:40:58 +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 Bump version to 0.3.0 2020-09-08 00:03:59 +02:00
meson_options.txt man: Add simple seatd(1) page 2020-08-08 14:54:25 +02:00
README.md Add platform support note to README 2020-08-01 17:18:53 +02:00

seatd and libseat

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

Currently supports Linux and FreeBSD. Alpha

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 deamon, 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/public-inbox@lists.sr.ht.