Document functionality of systemd without dbus
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 16.7k
- Forks
- 4.7k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 140
Description
Hello,
I`d like to cut down on anything expendable for an embedded setup. dbus is not seen as hard dependency, and some short tests indicate that systemd works without.
I would like systemd to use for socket-activation, passing socket fd to services, watchdog, journaling, and similar. Perhaps I want to use networkd too, but not sure on that yet.
I would however like to know what exactly is missing, if dbus is not available and whether this is a runtime-only decision or if compiling systemd with dbus disabled (forced, or detected to be not available) means that systemd will not use dbus even if it is available.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing systemd's documented behavior and build options around dbus, including the socket-activation, watchdog, journaling, and networkd functionality named in the issue. Document what is unavailable without dbus and whether disabling it at build time differs from runtime absence; the issue names no files or tests, so completion is a clear, verified explanation of those cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100