https://bugzilla.novell.com/show_bug.cgi?id=864894 https://bugzilla.novell.com/show_bug.cgi?id=864894#c5 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.blume@suse.com --- Comment #5 from Johannes Meixner <jsmeix@suse.com> 2014-09-12 11:38:07 CEST --- To avoid possible misunderstanding I like to point out that I wrote in comment#0: Because unit file names can be more or less random, it cannot work to use some kind of regular expression matching. This means the current systemctl wildcard feature as in # systemctl start cups* # systemctl stop cups* is helpful for an admin who types in systemctl commands but it is not the solution that I like to have. Furthermore it does not work for "enable/disable": ---------------------------------------------------------------------- # rpm -q systemd systemd-210-34.9.x86_64 # systemctl list-unit-files | grep cups cups-browsed.service disabled cups.service disabled # systemctl enable cups* Failed to execute operation: No such file or directory # systemctl enable cups.service # systemctl enable cups-browsed.service # systemctl list-unit-files | grep cups cups-browsed.service enabled cups.service enabled # systemctl disable cups* && echo ok || echo failed ok # systemctl list-unit-files | grep cups cups-browsed.service enabled cups.service enabled ---------------------------------------------------------------------- At least in systemd-210 the systemctl wildcard feature is in practice unusably broken. Even if the systemctl wildcard feature would work in practice it is questionable if tools like YaST support it. If not it also does not help to really solve the issue for normal users. In the end - from my current point of view - the systemctl wildcard feature is only helpful for an admin who types in systemctl commands but it is not a solution for normal users. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.