On Sat, 2024-09-21 at 09:49 -0400, Todd Zullinger wrote: > Patrick O'Callaghan wrote: > > 1. I run httpd via systemd for a small personal web service. This > > works. > > > > 2. I suspend my system overnight and wake it automatically in the > > morning). This turns out to be irrelevant, because the problem reported > > here occurs even when I do it manually. > > > > 3. On resuming, everything is up *except* httpd. > [...] > > I assume there's a systemd mechanism for getting httpd to wait for the > > network before resuming, but I've no idea how to accomplish this. > > Maybe give httpd.service(8) a read, particularly the section > "Starting the service at boot time" which covers adding a > drop-in file to make it depend on the network-online.target. > > Tried that with this drop-in: # cat /etc/systemd/system/httpd.service.d/override.conf [Unit] After=network-online.target Wants=network-online.target It made no difference. > I don't know if that's likely to work in your case, as I've > never run httpd on a system where I hibernate (or suspend), > but it's an easy thing to test. > > You might also consider using the httpd.socket activation > method. Then httpd will be started when a request for the > web service arrives. > > I'll take a look at that. poc -- _______________________________________________ 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
