On Sun, 2024-09-22 at 09:49 -0500, Chris Adams wrote: > For any service that doesn't handle active network changes, you should > stop it before suspend and start it after resume, after the network is > back online. I don't think network-online.target is sufficient for > this, I think it only activates at boot, not suspend/resume. I don't > know if there is an equivalent for post-resume; might have to write > something yourself that runs from an NM dispatch script.
Did that for a while, but it wasn't enough. This was typical: 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" 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" Sep 09 07:55:05 Bree systemd[1]: systemd-suspend.service: Deactivated successfully. <-- -------------------------------------------------------Where is this coming from? Sep 09 07:55:05 Bree systemd[1]: Finished systemd-suspend.service - System Suspend. Sep 09 07:55:05 Bree systemd[1]: Stopped target sleep.target - Sleep. Sep 09 07:55:05 Bree systemd[1]: Reached target suspend.target - Suspend. Sep 09 07:55:05 Bree systemd[1]: Stopped target suspend.target - Suspend. poc -- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
