On Wed, 26 Jan 2000 11:00:18 PST, aphro writes: >netscape uses a child called dns-helper and it tries to resolve some of >the netscape domains to see if DNS is working and because(i believe) of >the single threaded tcp portion of netscape this locks the browser until >the resolution is complete. this should only happen on initial startup >though. also when netscape is doing the lookup most of the time cpu % goes >to 100%
well, this naturally led me to think that keeping those records local should speed up starting netscrap, so I had tcpdump running while starting netscrap but I didn´t see a single packet (having, of course, made sure that those records aren´t cached). the netscrap-version I´m using is 4.61...so much for trying to smart it out :-/ cheers, &rw -- -- +++ EUnet/[EMAIL PROTECTED], 15.-17.2.'2k, Ebene02/Stand08 +++ ----- ___ - Robert Waldner EUnet/AT tech staff ---- / / / ___ ____ _/_ -- <[EMAIL PROTECTED]> RW960-RIPE --- /--- / / / / /___/ / --- ---EUnet EDV-DienstleistungsgesmbH--- -- /___ /___/ / / /___ /_ ---- Diefenbachgasse 35 A-1150 Wien - ----- Tel: +43 1 89933 Fax: +43 1 89933 533
