3 ms·

> Now is it systemctl restart myservice or systemctl myservice restart Actually long before that it was service restart myservice, which still works.

• morelisp 5y ago
  Unfortunately, it was `service myservice restart`, which is the wrong order if you want to be able to do multiple things at once (or even just align with any other `cmd subcmd args` program).
  • iso1210 5y ago
    service myserver restart /etc/init.d/myserver restart Seems the traditional order to me $ service myserver status $ service myserver reload $ service myserver restart makes perfect sense when tackling a single service
    • morelisp 5y ago
      The traditional order is more like # /etc/init.d/myserver reload unknown command reload # /etc/init.d/myserver restart unknown command restart # /etc/init.d/myserver stop myserver: warning: frobulator did not fully unfurl # /etc/init.d/myserver start myserver: still running on pid 1234 # kill -TERM 1234 kill: (1234) - No such process # grep "running on pid" /etc/init.d/myserver echo "$0: still running on pid `cat /var/run/myserver.pid`" # rm -f /var/run/myserver.pid # /etc/init.d/myserver start What you're calling "traditional" is the minor, purely UI-facade-level consistency we got after 10 years trying to clean that mess up. But actually we eventually gave up, and went on to invent something better.