Text 14, 65 rader
Skriven 2004-03-07 01:10:00 av Will Honea (1:106/2000.0)
     Kommentar till text 12 av Mike Luther (1:117/3001.0)
Ärende: Privoxy - Ijfire help?
==============================
Mike Luther wrote to Peter Knapper on 03/05

ML> Bottom line squared.  In that Injoy's firewall does not seem to
ML> require a  "resolv" file at all, and "resolv2" is always re-written 
ML> with each re-lease, the actual cleanup for a blown Injoy  disconnect
ML> with a remaining "resolv" file that isn't  supposed to be there is
ML> simple.  For a DHCP connection box  simply delete any such "resolv"
ML> file in \mptn\etc\ as part  of the boot run itself.  If it is needed
ML> for Injoy, it will  be replaced anyway as part of the Injoy
ML> connection process.

Mike, be careful with that statement - I still haven't confirmed what
file sequence the JVM uses - but it DOES do a DNS lookup and it DOES
cache addresses.  I've had to fight PolarBar over that one while I was
on the road using multiple dialup numbers as I went from place to
place.  Only know cure for JAVA apps on a re-lease where DNS changes is
to shut it down and restart ;-{
 
ML> Will's suggestion about homing the directory with a SET 
ML> statement is also needed, it seems, for some DOS and WIN 
ML> 3.1 applications to correctly work. But "resolv" in 
ML> \mptn\etc\ better not be there at all if not needed, and 
ML> for sure without the proper addressing to match "resolv2", 
ML> if it is!

Bob Eager had an interesting comment on usenet the other day about
resolv? files.  He refered to an RFC that seemed to say that the
convention was that the stack used resolv, reslov1, resolv2 etc. etc in
sequence until it found a working DNS.  HEARSAY MODE ON:  While OS/2
allows you to only set up 2 nameserver - primary and alternate - the
stack will actually use up to 3, cycling thru in the order they appear
in resolv?

I have to do some digging, but it looks like the stack itself uses
some sort of resolv? to handle any servce DNS service request - I know
that the socket libraries do NOT require a nameserver URL in the API
call sequence.

ML> Right now all is working again.  I have no idea what I will do if
ML> the primary  for-real DNS service fails again with Cox Tyler!  There
ML> may  be more yet to this problem I or we don't know still.   We'll
ML> see.

OK, now what do you do if  the Tyler center gets blown down by those
gentle Texas breezes laughingly refered to as tornadoes???

In-Joy has resisted my efforts to force the third one in from the
get-go, but I have an "after connect" script that I run to insert a
third (public) nameserver into resolv and it has gone thru the first
two a few times.  In fact, I tested by using 2 bogus DNS addresses and
dialup did in fact fall back to the third one I inserted.
 
ML> Thanks for the time you'all spent with this.  I deeply 
ML> appreciate learning from you folks and hope I've paid back 
ML> some of the obligations.

Sometimes you eat the bear, sometimes he eats you <g>.

Will Honea <whonea@codenet.net>

___
 þ KWQ/2 1.2i þ Save time - see it my way.

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