Hi all, I know this is the devel list, and that there are maybe more important things, but from my user perspective, this is really annoying: https://bugzilla.redhat.com/show_bug.cgi?id=748512
Are we only handful to find that 'systemctl list-unit-files' is just misleading, since users are dealing with units, not unit types ? Here is the my comment:
Another problem is when you want to list inactive units, for example to find out which ones you can start (that's what the bash completion script for systemctl tries to do). You then need 2 commands: systemctl list-units --all | grep ' inactive ' systemctl list-unit-files | grep ' disabled' As a user, I do not want to deal with implementation aspects, I want to deal with units (all of them). Why would the user have to issue a list-unit-files to find out which units he can start, and beforhand, how would he even know he'd have to do that ? Even the --help is not correct: there is no 'start' command for Unit File Commands. But obviously, unit-files *can* be started without being enabled. Also, there is currently no way to list all possible units in one command. I suggest Unit Commands and Unit File Commands are merged together. Then options like --files, --transient, --generated could be of interest for the list-units command.
BTW, systemd-bash-completion.sh is wrong at finding startable units. Cheers Foudil _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
