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

network interfaces: Reduce the start rate limit interval from 10 to 3 seconds #20222

Closed
wants to merge 1 commit into from

Conversation

spacekitteh
Copy link
Contributor

Motivation for this change

Sometimes, network connections fail a few times before they're stable. During boot, I don't want to have to wait 10 seconds in between attempting each phase of establishing a stable ethernet connection. So this lowers that.

@mention-bot
Copy link

@spacekitteh, thanks for your PR! By analyzing the history of the files in this pull request, we identified @wkennington, @groxxda and @kampfschlaefer to be potential reviewers.

@spacekitteh
Copy link
Contributor Author

Actually, "StartLimitIntervalSec = 3;" should also go into the "network-link-${i.name}" service in network-interfaces.nix, but the github web editor can't do that.

@kampfschlaefer
Copy link
Contributor

@spacekitteh When you have the branch (which you have since thats needed for pull requests), you can make additional commits and edit more files.

Be aware: when you only edit via web editor of github, your PR will most likely not fit this projects requirements: Multiple commits for one topic, no local execution of any tests and maybe some more…

So while I like the web editor of github, please give your PR better chances of acceptance by checking out your branch locally and testing it.

@@ -84,6 +84,7 @@ in
serviceConfig = {
Type = "oneshot";
RemainAfterExit = true;
StartLimitIntervalSec = 3;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably be a configuration option.

@fpletz
Copy link
Member

fpletz commented Nov 28, 2016

@spacekitteh What exactly is your problem here? Networking devices that are not yet available or just waiting for DHCP? In the latter case, dhcpcd would be the right place to change this. I don't think static configurations suffer from wait time at boot.

@spacekitteh
Copy link
Contributor Author

@fpletz I'm about 90% sure it's due to the device itself.

@mmahut
Copy link
Member

mmahut commented Aug 1, 2019

@spacekitteh Any update on this pull request?

@mmahut
Copy link
Member

mmahut commented Aug 19, 2019

Closing due to lack of activity, feel free to reopen this if needed.

@mmahut mmahut closed this Aug 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants