It depends on your distribution, but usually: Yes. If your distro is using systemd (almost, but not quite, all distributions nowadays), systemctl stop <servicename> is the preferred method.
If your distro does not use systemd, service <servicename> stop is the only way. This isn't limited to xcat, but true for any service. In practical terms, it usually doesn't matter because if you accidentally use service <servicename> stop on a new system, it will usually just redirect to systemctl, and vice versa. And on non-systemd systems, you'll know because typing the systemctl version will give you an error message. _______________________________________________________________________ Kevin Keane | Systems Architect | University of San Diego ITS | kke...@sandiego.edu *Pronouns: he/him/his*Maher Hall, 162 |5998 Alcalá Park | San Diego, CA 92110-2492 | 619.260.6859 | Text: 760-721-8339 *REMEMBER! **No one from IT at USD will ever ask to confirm or supply your password*. These messages are an attempt to steal your username and password. Please do not reply to, click the links within, or open the attachments of these messages. Delete them! On Thu, Nov 25, 2021 at 3:00 AM Christopher Walker <c.j.wal...@qmul.ac.uk> wrote: > > https://xcat-docs.readthedocs.io/en/stable/guides/install-guides/zypper/verify_xcat.html > says: > > > service xcatd stop[systemd] systemctl stop xcatd.service > > > Should we be using: > > systemctl stop xcatd > > these days? > > Chris > _______________________________________________ > xCAT-user mailing list > xCAT-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xcat-user >
_______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
