Hi all!
I've been a very happy user of diald for several years now, but it has
always given me a small problem. The first packet on the line always
gets lost, which means that I can't just run "sendmail -q" as my first
command, but has to do a finger or something just to bring the line up
first. That little workaround has worked well, until recently. Now I'm
running my own caching nameserver, and has upgraded my system to RedHat
5.2 (including fetchmail 4.7.7 and all RedHat patches) and diald 0.16.5.
Now the first packets to reach the outside world is from named, and it
has such a long timeout that the line goes down before it realizes it's
not going to get an answer! On my own machine that's something I can
live with, but I'm also setting up a small firewalled LAN here, and that
complicates things somewhat.
For now I'm using the script below to get a safe connection from my
other cron-scripts that sync my mail etc, but it doesn't help the rest
of my LAN. :(
Does any of you have any idea on what could be causing this? Thanks a
lot in advance.
/Basic
#!/bin/zsh
route -n |
tail +3 |
grep -v 192.168 | grep -v 127.0 | grep -v '^0.0.0.0' |
while read line; do
#echo We are connected.
exit 0
done
#echo We are not connected.
#date
# Try to establish a connection.
#
# ---> When diald brings up the line, finger hangs.
#
( (finger [EMAIL PROTECTED] |& grep unreachable) &&
echo We have no net today. &&
kill -HUP $$ && exit 1 ) &
# Wait for it to go up, then kill the finger.
sleep 40
kill %%
# Ok, the net is up, and everybody is happy!
exit 0
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
