Closed
Bug 40083
Opened 25 years ago
Closed 24 years ago
caching resolv.conf
Categories
(Core :: Networking, defect, P3)
Tracking
()
People
(Reporter: jmd, Assigned: gordon)
Details
Linux mozilla's async resolver seems to be caching /etc/resolv.conf, forcing
restarts when that file is changed. This is not normall application behaviour.
Is this known and wanted?
We don't have async dns lookups turned on for Unix yet. We are simply calling
gethostbyname (actually PR_GetIPNodeByName, which in turn calls gethostbyname).
Could you describe the symptoms in more detail?
Wan-Teh, any ideas?
|
||
Comment 3•25 years ago
|
||
As Gordon said, we are just calling
gethostbyname() or gethostbyname2() on
Linux.
I did a text search in the source tree
(using http://lxr.mozilla.org) for "resolv.conf"
and did find any match.
Marking this bug as INVALID. If this continues to cause a problem for someone,
please reopen with additional information so we can track down the cause. Thanks.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Target Milestone: --- → Future
actually a dupe...
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
*** This bug has been marked as a duplicate of 63564 ***
Status: REOPENED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•