Once upon a time, Todd Zullinger <tmz@xxxxxxxxx> said: > FWIW, apachectl in Fedora is a wrapper around systemctl, for > folks who have trained themselves to use apachectl. Ahh, didn't know that. > I'm not advocating for its use, as I think it's more work to > call it than it is to use systemctl consistently as for > other services. And for a small, personal webserver, any > benefits of using graceful are hard to imagine as important. Yeah, graceful on suspend is kind of a waste of time, just kill it ded. > But I don't _think_ it should cause httpd to be unmanaged -- > unless there's something more obscure I'm missing (which is > always possible)? What I meant was if you just "apachectl start" (when apachectl didn't call systemd), now you've got a background httpd that is not running under the relevant systemd service, so it's effectively "unmanaged" as far as the init system is concerned - systemd will consider httpd.service dead because that copy exited. "systemctl status" will show the system state as "degraded" instead of "running" (I monitor systemctl status in Nagios via SNMP). -- Chris Adams <linux@xxxxxxxxxxx> -- _______________________________________________ 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
