First Last Prev Next    This bug is not in your last search results.
Bug 126320 - restart nscd on writing out resolv.conf
restart nscd on writing out resolv.conf
Status: CLOSED DUPLICATE of bug 125712
Product: Fedora
Classification: Fedora
Component: dhcp (Show other bugs)
2
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jason Vas Dias
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2004-06-18 18:27 EDT by Havoc Pennington
Modified: 2007-11-30 17:10 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 14:04:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

  None (edit)
Description Havoc Pennington 2004-06-18 18:27:28 EDT 
When changing network interfaces, glibc keeps using the old
resolv.conf for a while. Dan says restarting nscd is how we're
supposed to fix this.
Comment 1 Bill Nottingham 2004-06-29 00:57:29 EDT 
Or not using nscd. :)
Comment 2 Havoc Pennington 2004-06-29 04:09:37 EDT 
Ah, we need nscd for caching the gecos info for users though...
Comment 3 Jason Vas Dias 2004-07-29 09:45:08 EDT 
We've been told by glibc developers that 
making nscd re-read resolv.conf on changes
is not an option .
If resolv.conf changes, restart nscd.


*** This bug has been marked as a duplicate of 125712 ***
Comment 4 Harald Hoyer 2004-07-29 09:59:40 EDT 
/etc/resolv.conf should probably only be accessed through viresolv
like visudo or addnameserver delnameserver like adduser for /etc/passwd
Comment 5 Red Hat Bugzilla 2006-02-21 14:04:09 EST 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.