Hi, Novice question: A service that can be run under systemd is given. On the one hand, it is possible to check the configuration before starting, e.g. "sshd -t". I would like a systemd configuration file that contains the configuration check. For this, the '[Service] ExecStartPre=' directive seems appropriate. However, I would like this to work when releasing a 'systemctl restart sshd.service'. My problem is this: Since, as far as I know, under systemd the restart is actually a stop and a start call issued consecutively, stop *stops* the service, and start is shocked to find that the service cannot be started due to a misconfiguration if someone edits the configuration as recklessly as I do. This would make restarting less trouble because the system will *work* with the old configuration. If I also adopt systemd's ExecStop feature, I feel like I'm pretty much going into a stinging forest. Can this task be solved? If systemd had ExecStop[Pre,Post] and/or config test, life might be simpler. Thank you in advance for your help. Regards, István -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
