launchd

Raised as a usability problem by 8 people on Hacker News over 16 years (2010–2025), in 6 threads.

People raised many different problems with launchd, but no single problem has yet been raised by 3 people in 3 different months and threads.

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 8 complaints

Failed bootstrap prints the same unhelpful 'Error 5' for every plist problem2025-04-03
Launchd documentation is so incomplete that setting up scheduled jobs wastes an hour2017-08-13
Launchd docs are so maddening and atrocious that they're hard to work from2017-07-10
Launchctl gives no useful output on whether commands worked, so operations are trial and error2016-10-12
Hard to find where a launchd job with a given label comes from2016-10-11
Binary plist files need special tools, making corruption and bad values hard to troubleshoot2015-07-21
Overlapping process type and scheduling terms are awkward and inconsistent to understand2015-07-21
Toggle to restart a process when it died didn't work as expected2010-05-25