Products · Product
systemd
Raised as a usability problem by 257 people on Hacker News over 14 years (2013–2026), in 203 threads.
- 1
- 1
- 2Config scattered across many tiny filesUnreviewed
- 3
- 1
- 2
- 3Binary logs are hard to findUnreviewed
- 4
- 5
- 6
- 7
- 8Config scattered across many tiny filesUnreviewed
- 9
- 10
- 11
- 12Pager text runs off screen by defaultUnreviewed
- 13
Every issue, all time, most people first
Journald output is hard to read and searchUnreviewed
20132026- Reading logs requires three commands, verbose flags and many searches to figure out2026-08-14
- Logging is needlessly complicated and log files are slow to read2026-06-03
- Journal logs silently fill the disk; defaults and config hard to discover2026-01-28
Service failures produce 50-100 lines of logs with no causeUnreviewed
20132026- Hard to find service logs; they are not easy to locate2025-03-14
- Logs show only restart errors, hiding why the service originally failed2023-08-01
- Service unit keywords are hard to discover and errors are hard to debug2022-10-27
Binary logs are hard to findUnreviewed
20132026- Forced to read logs through journalctl, which is slow and the binary format keeps changing2024-09-05
- Binary logs are hard to find, and failures are un-introspectable with standard tooling2023-02-28
- Getting the last few log lines takes tens of seconds because of the binary journal format2020-05-04
Debugging unit files requires memorizing magic commandsUnreviewed
20132026- Must look up unit file syntax every time; takes multiple tries and is hard to remember2022-12-08
- Unit files are scattered across many directories, so users must learn a tool or memorize paths to find them2022-10-01
- Must learn obscure commands to view simple unit configuration, rather than reading files2021-10-18
Background processes killed on logout unless obscure option setUnreviewed
20132026- Kills entire process groups, so terminal sessions and tmux panes disappear unexpectedly2026-02-22
- Kills users' tmux and background sessions on logout unexpectedly2026-02-03
- Programs keep running after logout, and users must use a task manager to stop them2019-01-29
Shutdown hangs for minutes with no manual skip optionUnreviewed
20132026- Shutdown hangs for 30 seconds to 10 minutes with no manual skip option2026-01-27
- Shutdown or reboot randomly hangs for minutes waiting on something, with no manual skip option2024-04-30
- Shutdown hangs for minutes waiting on something, with no manual skip option2024-04-26
Boot stalls with no info and no shell to fix itUnreviewed
20132026- A stalled startup task leaves the system non-interactive and the console useless2024-01-06
- Boot stalls with no useful info, and the user can't reach a shell to fix it2022-11-04
- Stuck boot jobs can't be cancelled from console; user can't disable scripts or diagnose boot delays2020-06-19
Config scattered across many tiny filesUnreviewed
20132026- Non-trivial config files are hard to debug and waste time2025-07-09
- Config split across many tiny files, hard to follow together2025-07-09
- Config scattered across many tiny files and a complex dependency model that is hard to debug2025-01-31
Commands and names are long, hard to type and rememberUnreviewed
20132026- Commands for basic tasks differ from the BSD systems the user knows, so they must relearn them2023-04-25
- Commands are hard to remember and clunky to type; common tasks undiscoverable without docs2021-03-31
- Commands and names are long, hard to type and non-memorable, with a steep learning curve for simple tasks2019-09-01
Man pages lack examples and file locationsUnreviewed
20132026- Documentation scattered across many manpages, hard to build a mental model2025-03-15
- Man pages are terse and split up, making a mental model hard to build2024-02-17
- Man pages are poor introductory docs; hello world example buried at bottom2021-10-18
Moving cron jobs to systemd is over-complicatedUnreviewed
20132026- Setting up a simple cron-like job is a poor experience2022-11-01
- Systemd timers are far more complex than cron, with corner cases even in simple uses2021-08-31
- Moving jobs from cron to systemd is over-complicated and hard to navigate2019-06-27
Hard to tell whether behaviour is expectedUnreviewed
20132026- Unpredictable and hard to debug in daily professional use2025-01-24
- Runs into insidious bugs despite the advertised easy interface2021-10-25
- Bugs are hard to debug and hard to tell if behaviour is expected2018-12-30
Pager text runs off screen by defaultUnreviewed
20132026- Pager text runs off screen by default; tailing logs requires waiting for full conversion2023-11-28
- Truncates log output by default and forces its own viewer instead of the system pager2018-08-10
- Overrides the user's own LESS settings for less, so pager behaves unexpectedly and is hard to diagnose2014-12-12
Service ordering is hard to debug without deep knowledgeUnreviewed
20132026- Hard to get service startup ordering right in non-trivial cases2024-04-30
- Getting service ordering and startup right is hard to debug and needs deep systemd knowledge2024-02-15
- Automatic dependency guessing starts services unexpectedly, forcing admins to dig through configs while debugging2014-01-20
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 50 complaints
- Uses only its own package's keys, so the new KSK isn't trusted and DNS fails without manual fixes2026-10-13
- Undocumented interactions between daemons cause days of hard-to-find debugging2026-09-18
- Reading logs requires three commands, verbose flags and many searches to figure out2026-08-14
- Config change for gpsd port silently overridden, needs extra systemd steps to fix2026-07-25
- Status command randomly pages output, blocking the terminal until user presses q2026-07-16
- Autodiscovery of separate partitions like /home is too limited, requiring manual fstab edits2026-06-30
- Bugs from accidental complexity and removed abilities with no warning2026-06-29
- Logging is needlessly complicated and log files are slow to read2026-06-03
- Calendar expression syntax is hard to read and parse at a glance2026-06-02
- Can't write a timer unit file from scratch without looking up the syntax2026-06-02
- Importing Docker-ecosystem images takes too many extra steps, so people fall back to Podman2026-05-31
- Editor layout would need to split into two panes for OpenRC, breaking a consistent UI2026-05-03
- Kills entire process groups, so terminal sessions and tmux panes disappear unexpectedly2026-02-22
- Breaks things often and deep issues are hard to fix, forcing reinstalls2026-02-03
- Mounts split across unit files, fstab and services; hard to know what works2026-02-03
- Kills users' tmux and background sessions on logout unexpectedly2026-02-03
- Mount warns about fstab edits and unmounted filesystems remount themselves unexpectedly2026-01-31
- Annoying to configure, breaks randomly, and hard to diagnose why2026-01-28
- Users struggle to find settings and log files; commenter argues it's just unfamiliarity2026-01-28
- Stop job message shows no indication of which job is stalling, so users can't tell what's wrong2026-01-28
- Logs aren't where expected; journalctl defaults are bad, needing long commands to filter2026-01-28
- Journal logs silently fill the disk; defaults and config hard to discover2026-01-28
- No simple global way to force shutdown after a timeout; must tune each service2026-01-28
- Shutdown hangs for 30 seconds to 10 minutes with no manual skip option2026-01-27
- Alternatives are hard to configure, maintain and debug in non-default use cases2025-12-15
- Systemd docs are poor, making the features hard to learn2025-09-20
- Two-way dependencies make the control graph hard to grasp overall2025-08-23
- Service files look like shell scripts and the manpage sample is confusing to read and maintain2025-08-19
- Systemd's user interface is awkward and warty to interact with2025-08-18
- Hard to tell which service is actually in control2025-07-24
- Components are hard to understand and hard to remove independently2025-07-11
- Non-trivial config files are hard to debug and waste time2025-07-09
- Scanning two months of logs takes about a minute, making it slow to use2025-07-09
- Config split across many tiny files, hard to follow together2025-07-09
- Killing Firefox to restore tabs takes seconds to clear its process tree under systemd2025-06-11
- System hangs at boot or shutdown, sitting idle with no feedback2025-04-11
- Waits minutes for failing units instead of failing fast, delaying boot2025-04-11
- Getting systemd journald logs into a central logging service was extremely painful2025-03-31
- Documentation scattered across many manpages, hard to build a mental model2025-03-15
- Hard to find service logs; they are not easy to locate2025-03-14
- Systemd gives no diagnostic help, so failures are bizarre and inscrutable to track down2025-03-04
- Working with it is miserable and a total pain to use2025-01-31
- Hits undocumented systemd behaviour that takes a day to debug2025-01-31
- Config scattered across many tiny files and a complex dependency model that is hard to debug2025-01-31
- Too many incompatible ways to configure networking on Linux, making it hard to settle on one2025-01-31
- Systemd-networkd fails often and systemd is undebuggable when it breaks2025-01-31
- Permission denied errors on mounting /proc were hard to diagnose across versions2025-01-26
- Unpredictable and hard to debug in daily professional use2025-01-24
- Hidden password prompts give no clue which service is asking or how to answer2025-01-20
- Unclear which filter or time range shows where things failed by default2025-01-19