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.

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.

Since, as you say, it's a "small personal web service" the
slight delay in the first request would likely be perfectly
acceptable (perhaps even unnoticeable).  That may side-step
the issue.

-- 
Todd
-- 
_______________________________________________
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

Reply via email to