The diald-connect in the RedHat contrib/.../i386 is *old* and should
not be used. The *new* diald-config-1.2.1-1 is under contrib/.../noarch!!
diald-config-1.2.1-1.noarch.rpm: install it and then install the
metered or unmetered packages. Be careful, as you may find that
rpm leaves .rpmsave files in your /etc/rc.d/rcX.d directories, causing
diald to be started twice. Once all that is ironed out, it should
come up. I get a little bit of odd behavior. Some in the clear light,
some in the dark. Try telneting to 127.0.0.1 - if it dials out, make
sure that your have a line for localhost in /etc/hosts AND that
localhost is listed FIRST if you have any other nicknames. Running
a caching nameserver seems to help, but I still get dial-out when
I boot (I assume this is a nameserver request, but I can't seem to
catch any traffic). More mysterious is the fact that it dials out
the FIRST time I start x-windows.\, but not subsequent times. I
avoid this double plague at the moment by using runlevel 5, but
I'd like to solve the problem. Last, but not least, after running
Netscape, diald never seems to hang up, even though tcpdump shows
no traffic. So, I'm using lynx, but need to solve the problem as
my wife needs to use Netscape.
Hope this helps everyone. I'd been going crazy until I found the
new diald-config.
Simon Hill
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
