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.

Sign up for GitHub

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

Jump to bottom

Cups is agnostic to resolv.conf changes #36

Closed
michaelrsweet opened this issue Apr 21, 2003 · 1 comment
Closed

Cups is agnostic to resolv.conf changes #36

michaelrsweet opened this issue Apr 21, 2003 · 1 comment
Labels
priority-low
Milestone
Stable

Comments

@michaelrsweet
Copy link
Collaborator

Version: 1.1.15
CUPS.org User: lurch.gmx

If the resolv.conf is changed after startup of cups (for example, by DHCP), cups still uses the old value(s) of nameserver for lookup.
@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

Believe it or not, this happens with all applications that use the resolver API... There is no standard way to re-read resolv.conf (or whatever is used by the local implementation...), so the only way around this is to stop and start cupsd after making changes to resolv.conf...

@michaelrsweet michaelrsweet added this to the Stable milestone Mar 17, 2016
This was referenced Mar 17, 2016
Closed
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority-low
Projects
None yet
Milestone
Stable
Development

No branches or pull requests
1 participant
@michaelrsweet