Text 9, 59 rader
Skriven 2004-03-04 15:59:00 av Will Honea (1:106/2000.0)
      Kommentar till text 3 av mark lewis (1:3634/12)
Ärende: Privoxy - Ijfire help?
==============================
mark lewis wrote to Mike Luther on 03/03

ml> whoa! i saw you guys mention resolv2 and in my experiance, that's
ml> seemingly  always been for the DOS stuffs whereas resolv has been
ml> for  the native OS/2 stuffs... understand, too, that i'm still  on
ml> Warp3 FP40 with NO networking FPs installed at all...  still
ml> original mpts and tcp/ip stuffs...  

Right idea, bass-ackwards detail.  resolv2 is the one OS/2 uses.

Mike got me started on this and the only resolv file on a clean system
is in \tcpip\dos\etc.  Way back when - Warp Connect AIR - there was a
mess that got itself cleared up nicely if you added a line to whichever
autoexec.bat you used for DOS/Winos2 apps that set %etc% for DOS apps
to be the same path as it was for OS/2 apps.  Just cut the
\tcpip\dos\etc completely out of the picture.  I noticed that my clean
ACP install did just that BUT:  the tcpcfg (or tcpcfg2 for tcpip 4.1+)
creates and maintains a resolv file in the \tcpip\dos\etc directory
anyway.  AFAICT, that's the ONLY app that uses that out-of-the-way
file.  Certainly DOS/WIN apps don't - unless their own %etc% is pointed
to \tcpip\dod\etc - for finding the etc files any other way would
implie a hard coded default path: not likely.  FYI, it took trying to
use a Winos2 net app that finally made this clear to me.  It couldn't
resolve addresses on a dialup link until I pointed it to %etc%.

Anyway, the %etc%\resolv that Mike is hollering about is in fact
created by In-Joy.  The IBM dialer also creates it (took me forever to
finally get that dinosaur to work).  The quibble I have with In-Joy is
that it creates a resolve file there, if none exists, by copying
resolv2.  Once resolv exists, it renames it to resolv.inj and creates a
NEW resolv file that lasts the life of the dialup connection.  This
temporary resolv file makes the nameservers supplied by In-Joy (either
as specified to In-Joy or as supplied by the ISP as dynamic values) the
ones to be used by everything for the duration of the session.  All
well and good except for one tiny detail:  when In-Joy closes the
connection down, it deletes resolv and renames resolve.inj back to
resolv.  The fly in the ointment is that if that original resolv
happens to be one left by a system crash (or an In-Joy crash) it will
contain the dynamic values put in by the aborted In-Joy session and the
next invocation will wipe out the original copy that synced with
resolv2.  Not a big deal unless you use a variety of nameservers and
you happen to always need access to a particular one (as in a large
corporate LAN) in addition to the dynamic dialup DNS.  In that case,
crash In-Joy and you done bit the bullet for the in-house DNS.

There are ways around this - make a fresh copy of resolve from resolv2
during tcpip startup and again during In-Joy initialization, etc - but
it is a bit of a tarball.  

In short, ignore \tcpip\dos\etc\resolv and set all apps to use the
same path.

Will Honea <whonea@codenet.net>

___
 þ KWQ/2 1.2i þ Karaoke: Japanese for "tone-deaf drunk with a microphone."

--- Maximus/2 3.01
 * Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)