Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not After=network.target the -display & audiodetector services #562

Merged
merged 1 commit into from
Dec 11, 2023

Conversation

rtertiaer
Copy link
Contributor

During some network oddities where the network initialization does not start or fail quickly but hangs for a long time, the display and audiodetector services also hang. I've removed that "weak dependency". This potentially allows us to give better feedback during bootup.

This still needs to be tested, in particular because of the display service potentially having a true dependency on networking at the moment; thus, I've filed this as a draft for now.

@rtertiaer rtertiaer requested a review from Lohrer December 11, 2023 17:57
@rtertiaer rtertiaer changed the title Do not After=network.service the -display & audiodetector services Do not After=network.target the -display & audiodetector services Dec 11, 2023
@rtertiaer rtertiaer force-pushed the no_after_network_systemd branch from 52b9f35 to be36588 Compare December 11, 2023 18:07
@rtertiaer
Copy link
Contributor Author

With un-bonded grounds, the behavior of the display did not change. With bonded grounds, this briefly starts with "None" for the interface stuff, but otherwise boots up normally & "just works".

I think we're also guarded against any potential exceptions with systemd restarting the service over time.

But all in all, I can't demonstrate that this PR changes behavior at all, which could be good or pointless in this context 😂 It still feels more correct to have these services not necessarily wait for the network to be available; they should not have any hard dependencies on the network.

@rtertiaer rtertiaer marked this pull request as ready for review December 11, 2023 18:47
@rtertiaer rtertiaer force-pushed the no_after_network_systemd branch from be36588 to 2ca1da8 Compare December 11, 2023 20:32
@rtertiaer rtertiaer merged commit 2ca1da8 into develop Dec 11, 2023
3 checks passed
@rtertiaer rtertiaer deleted the no_after_network_systemd branch December 11, 2023 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants