🚀 go-pugleaf

In article <Doxr5r.A9J@midway.uchicago.edu>,
fugue <fugue@cicero.spc.uchicago.edu> wrote:
>In article <DovuFn.Iy9@midway.uchicago.edu>,
>fugue <fugue@cicero.spc.uchicago.edu> wrote:
>>Hi all...
>>  I've been watching the group for a while hoping an answer to my question
>>would appear (as well as using DejaNews to check back in time...), but none
>>has to date, so I'll ask.
>>
>>First, a bit of tech setup info:
>>A1200, 50MHz 68030 w/MMU, 25MHz FPU, 8 fast, 2 chip, 1.2 gig SCSI, 14.4k modem.
>>AmiTCP 4.0 Demo
>>PPP Unregistered (the newest release, whatever version it is...)
>
>1.45   I checked. :)
>
>>
>>Anyway...I used to run AmiTCP over a non-dynamically-assigned SLIP connection
>>(using cslip...I had a permanent IP), and everything worked absolutely fine.
>>
>>Now, the Powers That Be(TM) decided that my little pet IP should go away, so
>>I'm being forced to used a dial-up, dynamic PPP connection, which hangs up
>>every 3 hours.  I installed PPP, and used one of the many dialer programs
>>out there (I'm at work now and can't recall the name, but it's very nice,
>>with an intuitive GUI and easy scripting...whichever it is, I love it).
>>
>
>
>SLIPCall...I checked again. :)
>
>>Anyhow, for some reason, there are several problems cropping up.
>>1)  in ENV:, my .config file keeps changing back to my old one, even though
>>    it no longer exists in ENVARC:, and none of my scripts touch it.  I have
>>    to hand-edit the thing each time.
>>
>
>Ok...I got this fixed by reinstalling everything. *sigh*
>
>>2)  DNS is kaput.  For some reason, the file in db: which is responsible for
>>    assigning DNS names/addresses (again, I'm at work and blanking on the name)
>>    keeps getting reset to default.  I have to overwrite it from backup to get
>>    it to work, and even then DNS sometimes refuses to work.
>>
>
>
>It's the resolv.conf.  Something keeps backing it up (resolv.conf.backup), but
> every time I start from a warm-boot, my resolv.conf contains no domain names,
> and a nameserver address of 0.0.0.0.
>  Additionally, when AmiTCP is first started, I'm not logged inm properly.
>I end up having to do it manually, then copy the resolv.conf.backup to 
>resolv.conf, kill AmiTCP and SLIPCall, then restart SLIPCall.  After that,
>everything's kosher.  I just can't figure out what's causing it to do that.
>

Ok.  I figured out what was going on.  It's SLIPCall (thanks to SnoopDOS...
I always have it sitting on the workbench, didn't think to use it.  *sigh*).
SLIPCall has a "built-in" startnet script of it's own, and one of the things
it does is create its' own resolv.conf. when it starts up.  This is fine if
you use one DNS, but our WAN config is set up with multiple nameservers.

After giving it a lot of thought, although I like the GUI of SLIPCall, I'm
just going to switch to a bunch of scripts, using PPP's own builtin dialer.
This is probably better anyway, as my provider has a 3 hour connection time
limit, and I can use ReStarter to keep my connection up if I go the PPP dial
script route.  Not graphical, but workable.  Maybe I can manage to write a
program that monitors the ppp.device status and updates an appicon to indicate
login time/time remaining/online status.  (My modem is not within my field of
view, so I can't keep an eye on the status lights without doubling over).

Anyway, thanks for the help.

-fugue


-- 
   ___"...and who by brave ascent?  Who by accident?  Who in solitude?    
  / __)Who in this mirror?  Who by his lady's command?  Who by his own hand?
 / __) / (_' ) / / '_) Who in mortal chains?  Who in power?  And, who shall I
l_/ /___/(__/___/___) say is calling?"   --Leonard Cohen, "Who by fire?"