Tim: > > Bearing in mind that even *then* there have been cases of the network > > not actually being up and running before being declared it was. I'm > > beginning to think we need either a post-boot target, or at least an > > improvement on the network is up decision making. Benny Lyne Amorsen: > network-online.target is documented as being "best effort". In the > current days of very complicated networking, there is no way to know for > sure that the network is actually up or what it means for network to be > up. Yes, there's multiple interfaces with differing uses. An internal mail system might only need localhost, and that can come up quite quickly. Something else might need PC to PC intranet working, which may take longer, and depend on both ends coming up, before it's ready for use. And then an internet connection becoming useful might take even longer. A network is UP flag could individually indicate each one, and your services could pay attention to *your* choice of which network they needed. Or it could be an everything is ready now flag, though that could stymie a bunch of things that really didn't need to wait for that last thing to come alive. All my LAN traffic, for instance, doesn't need any internet service at all for it to do whatever it's going to do. But just the first thing coming up declaring the network is up is probably no use. There was a whole chain of events with the original poster. When the system comes up as multiuser, start up postfix. But postfix must first wait for the network (or at least the bits of it needs) to come up. I've had that issue with NTP. If you tried to start it before the network (which was its default), it'd start, find there's no network, and go into a self-contained mode and never try to access the network again. There's one or two services that I've put restart rules for when the network statuses change, and I've done that as network change rules, not rules for those services. -- uname -rsvp Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. -- _______________________________________________ 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
