News for hackers. Stuff that matters.
Re:Show HN: Interactive systemd (a better way to work with s... by brontitall on Saturday January 18, 2025 @04:32PM (#42751590)
Doing it the way it does allows specifying multiple services.

systemctl status myapp mydb

Re:Show HN: Interactive systemd (a better way to work with s... by IgorPartola on Saturday January 18, 2025 @07:36PM (#42752625)
I would rather do that as two commands than to scroll to see the output of each.
Re:Show HN: Interactive systemd (a better way to work with s... by okanat on Saturday January 18, 2025 @08:48PM (#42752922)
There is no output for success.
Re:Show HN: Interactive systemd (a better way to work with s... by BikiniPrince on Saturday January 18, 2025 @09:45PM (#42753161)
Only failure is rewarded!
Re:Show HN: Interactive systemd (a better way to work with s... by egberts1 on Sunday January 19, 2025 @05:57AM (#42755942)
NOBODY ask for a status of two services.

Hence the verb-last CLI rulez!

Re:Show HN: Interactive systemd (a better way to work with s... by autoexec on Saturday January 18, 2025 @05:32PM (#42751946)
Why not allow for both and accept the option at any location?

Something like:

systemctl --stop myapp mydb

systemctl myapp mydb --stop

Re:Show HN: Interactive systemd (a better way to work with s... by bronson on Saturday January 18, 2025 @05:48PM (#42752050)
unnecessary flexibility brings unnecessary bugs
Re:Show HN: Interactive systemd (a better way to work with s... by Ayesh on Saturday January 18, 2025 @09:31PM (#42753104)
All `--` strings should be "options". Starting/stopping a service is not an option, it's a command. I don't enjoy `pacman` for this very reason.