- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
SystemD Pilot is a desktop application for managing systemd services on GNU/linux machines. The app is very lightweight and supports common tasks such as starting and stopping systemd services.
It can also show detailed status for each service.
Features: List services
Filter by running state
Start, Stop, Restart, Enable and Disable services + show status for each service
Create override configuration for any unit file using the edit button
Option for reloading systemd manager configuration (systemctl daemon-reload)
Easy search. Just start typing and the app will find relevant services
Lightweight
Available for download as deb, rpm and AppImage
Integration into GNOME desktop (libadwaita)
Made with love for the FOSS community. Please give it a try and share your thoughts.
You must log in or register to comment.
I’d prefer to manage systemd profiles in the rearview.
Cool. I have been using the built in YAST2 GUI services on OpenSUSE. But for other machines COCKPIT webgui uses systems to view and manage services.
100% Python, nice.
man wtf. I’ve been searching for something like this.
aw fuck, I thought this was a web interface like cockpit. ok nvm :(
What’s wrong with cockpit?
This is impressive I love to see another addition to the Libadwaita family
.
NO! NO, I WON’T HAVE IT!
I will not give up my command line, obscure, non-obvious commands that control my machine!
It is an abomination that I don’t have to search for, and then wade through hundreds of AI generated pages of useless information just to show me what services are running with systemd!
I am seriously considering starting my own startup system. I am thinking I could initiate (init) runlevels to start subsystems at various stages. If anyone is interested, hit me up.
wade through hundreds of AI generated pages of useless information
I personally find the best use of AI is to read those pages of useless information and summarise what I actually want to know.
Google: " hugo, show total number of posts not including pages " = advertising, a billion pages of partially but not entirely relevant information that takes ages to wade through.
Gemini: same question: Clear explanation and working examples in seconds.
They’re both google, but one knows what I’m actually trying to say and doesn’t (yet) push advertising at me.
Maybe you can script everything, with convoluted interconnections that are impossible to troubleshoot. Now that would be the way to control all the systems behind impenetrable obfuscation and keep those dratted normies from understanding anything.
I can’t tell if you’re taking the piss or not about re-implementing initscripts.
My job here is done 😉
this dude boots 😎
oh it’s not an official thing, that could probably use some more clarification as the name makes it sound like something developed by the systemd people
Nice i will try it out.
Thanks :) Hope you find it useful
Really cool bro. Always loved GUI for command line utils!
Looks neat, does its job.
If you’re a power-user looking at this, you can also look at https://github.com/rgwood/systemctl-tui which is somewhat similar but seems to be more useful (for now), also showing the service logs and being easily navigable with a keyboard.
Oooh this will be perfect for a bunch of stuff I do.
Can you create new services or do you still need to create the .service file manually?
What about .timer files?
I’ve been thinking about a “create new service” feature but I’m not sure about two things: 1.how useful it can be 2.how to implement this to actually make life easier for end users
Adding a generic template would not be difficult.
Making life easier for end users means more documentation about what you are doing. I mean that’s the main difference between Commandline and a GUI.
Oh look Avahi Service, let’s stop it, what does it mean to stop it.
Creating a new Service, sure but what is needed, are there examples? Formfill lines with a hint what’s needed, maybe some dropdown entries?
You got what I mean.
Even if the new service is “just” a text field for code + the name of the service. If it saves it in the right location for you its useful. Not having to fiddle with that stuff as an end user is nice.
Done! Chack out the latest version.
I tried it yesterday and it looks great. And I have three pieces of feedback:
- Ctrl + F doesn’t always bring up the search.
- I’m not seeing my custom services (one I made with and one without this tool)
- When making a service it would be nice to have a tool tip explaining what every line does. Though I can understand (and there is an argument for) not including this as this can simply be out of scope. (4. Please try to have it added to the fedora RPM so it can get auto updated :) )
Thanks for your feedback. Did you try version 3.0?
I would absolutely use it. In fact creating and editing services would be the primary selling point IMO. It doesn’t need to be much “easier” than doing it in the terminal or file explorer, to me the primary benefit would just be the ease of use of creating, loading, and starting a new service all in one place.
I think a generic template would be great.
You could turn the whole thing into a giant GUI settings screen, allowing navigation to an exectuable, after which you could provide some of the most typical options as sliders, number fields, switches, or whatever is suitable. But that would be a large amount of work, and I’m not sure it would simplify things much.
The starting point should just be a text field, but with a link to the service file docs for help/reference.
Brilliant thanks for your feedback and thoughts. Will look into this.
As far as i can tell a full gui for systemd service files would be practically impossible. But a template ui would be sick, maybe something like an app autostart template could look like this:
Program: Launch options: When: early/normal/login/graphical-start Restart: never/once/alwaysJust spitballing here though.
This was added to the latest version. You can now quickly start a new service from the app.
awesome! Tysm
And the RestartSomethingInterval=0 option so systemd keeps restarting the program like an obedient machine it should be, not give up because it’s tired
Just having something that shows the field options and formats it correctly would be fantastic. Tooltips and all that could be added later to lower the bar of entry for new users.
What license are you offering it under?
GPL v3.
The only right choice! Thanks!
Btw add license to the repo and license info to readme
Thanks, will do.
Thanks for this! Works pretty well when testing -
I switched to linux a little over a year ago and went with MX Linux because they have great GUI tools for windows refugees like myself, and because they don’t like systemd over there they use cron jobs. Now, having switched to Nobara I’ve just installed both SystemD Pilot here, but also found KCron, a KDE Cron configuration module which allows for the same functionality as what I’m used to.
If I just want to setup a “when system starts” daemon, is there really any difference in using one over the other? I guess it’s possible to shut down services more gracefully?In any case, great job on this utility.
Services are the more standard way of doing that. They are more resilient and you could troubleshoot more easily. Glad you are happy with systemd Pilot. Feel frree to share your thoughts or ask for new features.
