Once upon a time, Patrick O'Callaghan <pocallaghan@xxxxxxxxx> said: > On suspend: > Sep 09 01:01:44 Bree systemd[1]: Starting systemd-suspend.service - System Suspend... > Sep 09 01:01:44 Bree systemd[1]: httpd.service: Sent signal SIGWINCH to main process 332400 (httpd) on client request. <-- From "apachectl graceful-stop" You probably would be better to "systemctl stop httpd.service". > Sep 09 01:01:44 Bree systemd-sleep[521955]: Performing sleep operation 'suspend'... > > and on resume: > > Sep 09 07:55:05 Bree systemd[1]: httpd.service: Sent signal SIGUSR1 to main process 332400 (httpd) on client request. <------ From "apachectl graceful" And then "systemctl start httpd.service" (but maybe after a sleep to allow the network a chance to resume?). By stopping and starting it outside of the systemd unit, it turns into an unmanaged service. > Sep 09 07:55:05 Bree systemd[1]: systemd-suspend.service: Deactivated successfully. <-- -------------------------------------------------------Where is this coming from? It's coming from the systemd-suspend.service stopping (because you resumed). That's a normal part of resume. -- 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
