2 ms·
So that it's easier to bring up/down a number of related service units with single actions. Example: systemctl stop smbd nmbd ; systemctl start smbd nmbd It i
by mjevans 11y ago
So that it's easier to bring up/down a number of related service units with single actions.
Example: systemctl stop smbd nmbd ; systemctl start smbd nmbd
It isn't that the operation is the /middle/ parameter, it's that you have invocation action //LIST//
- nickysielicki 11y agoThe point of OP's link is that the novelty of systemd is that you can compose chains of dependencies and how that saves time and effort. So why should it be a common operation for the enduser to start and stop a list of related services? Instead of having to type and remember them individually, I should add a BindTo line in my service files and let systemd handle it. It's like the frontend for systemd is optimizing for a situation that it is supposed to prevent. And anyway, there's no unixy reason the variadic argument couldn't be in the middle. cp, for example, has <command name> <options> <variadic list of files to copy> <single dir to copy to>