Skip to content

[3.0] Respect attempts and timeout from resolv.conf #231

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

Draft
wants to merge 3 commits into
base: 3.x
Choose a base branch
from

Conversation

WyriHaximus
Copy link
Member

@WyriHaximus WyriHaximus commented Feb 22, 2025

The commits in this PR add representation, parsing, and utilisation of attempts and timeout options from resolv.conf.
Based on https://man7.org/linux/man-pages/man5/resolv.conf.5.html the limits for both options have been silently capped, and for both, the assumption is made that the lowest possible value is 1.

Builds the foundation for #231 that will implement #158. Building on top of #187, #179, #180, and many others.

@WyriHaximus WyriHaximus added this to the v3.0.0 milestone Feb 22, 2025
@WyriHaximus WyriHaximus changed the title [3.0] Respect attempts and timeout from resolv.conf [3.0] Respect attempts and timeout from resolv.conf Jul 9, 2025
…options

The two current supported options, `attempts` and `timeout`, have their min (assumed to be `1`), max, and default value as specified on https://man7.org/linux/man-pages/man5/resolv.conf.5.html set.
@WyriHaximus WyriHaximus force-pushed the 3.x-respect-attempts-and-timeout-from-resolv.conf branch from d75f553 to c78b412 Compare July 9, 2025 05:44
Adding parsing logic to the `Config` class that respects values as specified on https://man7.org/linux/man-pages/man5/resolv.conf.5.html in such a way we can easily expand the list to add `search`, `ndots`, and more in follow up PRs. As per https://man7.org/linux/man-pages/man5/resolv.conf.5.html both values are silently capped and are not allowed to go below 1.
While setting up the executors we will now use the `Options` class to pass in formally hardcoded values. This won't impact current behavior unless `resolv.conf` other than default values.
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.

1 participant