Closed Bug 63564 Opened 23 years ago Closed 22 years ago

Conn: DNS: (UNIX) /etc/resolv.conf read only at startup

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED DUPLICATE of bug 117628
Milestone:
mozilla1.2alpha

People

(Reporter: mpalczew, Assigned: gordon)

References

(
URL
)

Details

on a 2000121210 build of mozilla for linuxppc. It appears that if I change the
ip of my nameserver in /etc/resolv.conf mozilla needs to be restarted for the
changes to take affect. Netscape 4.75 doesn't exibit this behaiviour if
/etc/resolv.conf is change Netscape will start looking at the new name server.
*** Bug 61434 has been marked as a duplicate of this bug. ***
*** Bug 61434 has been marked as a duplicate of this bug. ***
dns bug
Assignee: neeti → darin
Blocks: 61683
This is quite strange, since on Linux, mozilla just calls gethostbyname from
libc.  Can you give anymore details... are there any error messages that appear
on the console?  thx!
Darin: See bug 40083
marked resolved invalid, but seem to be a dupe of this one.

...interesting... i wonder if it is some sort of wacky side effect of using
pthreads?  what version of libc are you using?  and with which kernel?  thx!
on my redhat 7.0 linux box, changes to /etc/resolv.conf only take effect when
a process is started.  therefore, there doesn't seem to be much we can do to
avoid this problem short of spawning a DNS helper process a la NN4.
marking WONTFIX
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
verified WONTFIX
Status: RESOLVED → VERIFIED
Fixed platform for searchability.
Hardware: Macintosh → PC
*** Bug 78999 has been marked as a duplicate of this bug. ***
*** Bug 82468 has been marked as a duplicate of this bug. ***
Keywords: mostfreq
*** Bug 40083 has been marked as a duplicate of this bug. ***
changed summary
Summary: mozilla doesn't watch /etc/resolv.conf → Conn: /etc/resolv.conf read only at startup
DUPLICATE SUMMARY:
61434 - using wvdial 1.41, /etc/resolv.conf changes on dialup.
78999 - ppp connect using rh ppp under redhat 7.0
        FreeBSD with a PPTP (pptpclient) VPN
82468 - not a DUPE.
Summary: Conn: /etc/resolv.conf read only at startup → Conn: (UNIX) /etc/resolv.conf read only at startup
*** Bug 90913 has been marked as a duplicate of this bug. ***
*** Bug 104564 has been marked as a duplicate of this bug. ***
*** Bug 104753 has been marked as a duplicate of this bug. ***
*** Bug 104857 has been marked as a duplicate of this bug. ***
For the record, this is proper (well, normal) libresolv behaviour on UNIX. The
file is read once, on the first resolve call.
*** Bug 116903 has been marked as a duplicate of this bug. ***
*** Bug 120730 has been marked as a duplicate of this bug. ***
an interesting note.  under redhat 7.2 (glibc-2.2.4), toggling the
offline/online button causes mozilla to re-read /etc/resolv.conf.  i'm not sure
how this is working.... and, i don't believe it ever worked before.
I have been relying on the Offline/Online toggle for news server access for some
time now.  If I go offline, then online again in the same session, my news
server cannot be found.  Toggling 'Work offline'/'Work online' brought it back.
 Recently (within the last week or two) this has ceased to work, and I am back
to shutting Mozilla down and restarting to get to me news server.
Further to my last comment: should I report this as a new bug.  It is a gigantic
pain in the backside for users like me who are on dialup connections, and who go
on and off line frequently.  Until a few days ago, I had a workaround with the
Work Offline/Work Online toggle.  Now I have to blow mozilla away and restart
whenever I connect.  Is there another workaround.  If not, is a reversion to the
previous behaviour possible.
Status: VERIFIED → REOPENED
Resolution: WONTFIX → ---
cc'ing gordon since he was the proud owner of the patch that "broke" this ;-)
Darin, I'll take this. It may turn into a dup of one of my other bugs anyway.

We should be able to at least recover the offline/online toggle functionality,
but hopefully we can do better (stat and reread resolv.conf on gethostbyname
errors or timeouts, something like that).
Assignee: darin → gordon
Status: REOPENED → NEW
Target Milestone: --- → mozilla1.0
Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+,
topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword.  Please send any
questions or feedback about this to adt@netscape.com.  You can search for
"Moving bugs not scheduled for a project" to quickly delete this bugmail.
Target Milestone: mozilla1.0 → mozilla1.2
Plussing for 1.0: large win for dialup users, I think we have a patch floating
around from the OEone guys, and if not I'll extort one out of someone.
Keywords: mozilla1.0+
Shouldn't this be a dupe of bug 64857 or vice-versa?
should use res_init(3)?

The situation seems to have improved.  If I am on-line when I start mozilla, I
seem to be able to go offline and online again without losing my ability to
access the net.  I don't think this was always the case.  However, if I am
offline when I start mozilla, I cannot access the net after going online.  Work
Offline/Work Online does nothing.  I have to restart.  Some time ago now, I used
to be able to gain access by toggling offline/online.
I think this is fixed by 117628's righteous res_ninit patch.

I'm (forward) duping, please reopen if it's not really resolved.

*** This bug has been marked as a duplicate of 117628 ***
Status: NEW → RESOLVED
Closed: 23 years ago → 22 years ago
Resolution: --- → DUPLICATE
VERIFIED/dupe.
not completely fixed, but you can follow the dupe chain to bug 166479.
Status: RESOLVED → VERIFIED
QA Contact: tever → benc
Summary: Conn: (UNIX) /etc/resolv.conf read only at startup → Conn: DNS: (UNIX) /etc/resolv.conf read only at startup
You need to log in before you can comment on or make changes to this bug.