I had a similar problem, but I found that diald would log an entry in
/var/log/messages that looked as follows:
Sep 9 09:10:33 diald[24583]: Link died on remote end.
... so in my ip-down script I put the following:
#!/bin/sh
ISP_HOST=xxx.xxx.xxx.xxx # Your ISP's IP address
# Give diald a chance to log what happened:
sleep 2
# Now check the logs:
/usr/bin/tail /var/log/messages | /usr/bin/grep "Link died on remote end." \
>/dev/null
if [ $? -eq 0 ]; then
ping -c 1 $ISP_HOST >/dev/null
fi
... it has worked pretty well for the past few weeks.
--Miguel
In message <[EMAIL PROTECTED]>, Jon Miner wr
ites:
>At 11:54 AM 9/9/99 , [EMAIL PROTECTED] wrote:
>>
>>Yes, but its called only once, when the link is brought up.
>>I need my script to be called periodically while the link is being forced
>>up.
>
>Just start something in ip-up that periodically does something. My
>favorite is to just send a single 1-byte ping every 20 seconds. ip-down
>just kills the ping job.
>
>you could even dynamically add a cron job.
>
>jon
>
>--
>Jonathan J. Miner----------------------| [EMAIL PROTECTED]
>Network Systems Technology | 608/262.9655
>Division of Information Technology | 3149 Computer Science
>University of Wisconsin, Madison | 1210 W. Dayton St.
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-diald" in
>the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
