Would the following work:
- Introduce new network-has-address event.
- Change our scripts to emit this event at the same time as network-static-up when we have a non-loopback interface configured.
- Add a Network Manager hook to emit it too.
- Implement a fallback job that times out after 2min (similar to that for network-static-up but without holding the boot).
The rational for a separate event being that I don't think we want to delay the boot on wireless-only desktop machines by whatever time it takes to connect to their wireless network, only the services explicitly requiring it should be delayed.
I wouldn't actually be against not having a timeout at all as these services will typically fail whenever we reach that timeout anyway.
Clint: Any progress on this?
Would the following work:
- Introduce new network-has-address event.
- Change our scripts to emit this event at the same time as network-static-up when we have a non-loopback interface configured.
- Add a Network Manager hook to emit it too.
- Implement a fallback job that times out after 2min (similar to that for network-static-up but without holding the boot).
The rational for a separate event being that I don't think we want to delay the boot on wireless-only desktop machines by whatever time it takes to connect to their wireless network, only the services explicitly requiring it should be delayed.
I wouldn't actually be against not having a timeout at all as these services will typically fail whenever we reach that timeout anyway.
Does that make sense? did I miss something?