DMdmd·Mar 14, 2025
I would love to see something like https://github.com/isd-project/isd but for systemd timers.
In Working with Systemd Timerskainctl
isd
Python2025–2025
kainctl / isd
isd
isd (interactive systemd) – a better way to work with systemd units
4Distinct people
4Mentions
0Explicit recommenders
2.2KGitHub stars
What to know before exploring
What it is
isd (interactive systemd) – a better way to work with systemd units
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week4 dated mentions
Observed mentions: 2025-01-18 17:19:34 UTC to 2025-03-14 16:41:26 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jan 13 | 2025-01-13 00:00:00 UTC | 2025-01-20 00:00:00 UTC | 3 | 0 | 3 |
| Jan 20 | 2025-01-20 00:00:00 UTC | 2025-01-27 00:00:00 UTC | 0 | 0 | 0 |
| Jan 27 | 2025-01-27 00:00:00 UTC | 2025-02-03 00:00:00 UTC | 0 | 0 | 0 |
| Feb 3 | 2025-02-03 00:00:00 UTC | 2025-02-10 00:00:00 UTC | 0 | 0 | 0 |
| Feb 10 | 2025-02-10 00:00:00 UTC | 2025-02-17 00:00:00 UTC | 0 | 0 | 0 |
| Feb 17 | 2025-02-17 00:00:00 UTC | 2025-02-24 00:00:00 UTC | 0 | 0 | 0 |
| Feb 24 | 2025-02-24 00:00:00 UTC | 2025-03-03 00:00:00 UTC | 0 | 0 | 0 |
| Mar 3 | 2025-03-03 00:00:00 UTC | 2025-03-10 00:00:00 UTC | 0 | 0 | 0 |
| Mar 10 | 2025-03-10 00:00:00 UTC | 2025-03-17 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
4 sourcesI will investigate it!
https://github.com/isd-project/isd/issues/6
In Show HN: Interactive systemd – a better way to work with systemd unitsAt long last, systemd-client: merry meet! Next step is such a TUI for non-Linux such as macOS, FreeBSD, Windows. For macOS I use LaunchControl.app but it isn't a TUI.
Just one thing: I had to do
$ uv tool install git+https://github.com/isd-project/isd
instead of
$ uv tool install https://github.com/isd-project/isd/isd@latest
and uvx wouldn't work at all, version: uv 0.5.21. That said, uv is way more quick than pip(x) so I just switched.
In Show HN: Interactive systemd – a better way to work with systemd units> If you have nix installed, this AppImage will not work! Either use the nix or uv installation instructions!
Is this really true? I understand why it does not work on NixOS (I tried just out of curiosity and it seems like it is unable to exec the host systemctl for some reason) but I don't think there's any reason it wouldn't work on other OSes that merely have Nix installed.
Interestingly though, on Nix v2.24.11, I can't use the provided Nix command either:
$ nix run https://github.com/isd-project/isd
error:
… while fetching the input 'https://github.com/isd-project/isd'
error: Failed to open archive (Unrecognized archive format)
Even if that did work (you could adjust it into a Git URL to make it work) it would probably not be ideal since Nix has a native GitHub fetcher that is more efficient. I thin
Read the rest
k this should be the actual Nix command:
nix run github:isd-project/isd
Anyway, this is cool. I actually wanted to make a similar thing using systemd's DBus API and Qt instead of a TUI and even started writing code for it, and if you wanted to I'm sure you'd find that the DBus API probably provides all of the functionality you would need (admittedly it is a lot easier to just call `systemd -H` than to implement your own SSH tunneling, though.) It kind of frustrates me that systemd and modern Linux in general is absolutely teeming with data and interfaces that could be exposed and make administering systems, especially desktop systems that were traditionally very inscrutable, much easier. e.g. in the past, how did you know what was going on when an xdg autostart app failed? Now with systemd running xdg autostart apps in some desktops, it would be really easy to provide a GUI that can show you the failed autostarts and even provide a GUI log viewer, and yet somehow, such a tool does not seem to exist, at least in the realm of things that are maintained and relatively feature-complete. Rather frustrating.