Hi!
On Fri, 10 Sep 1999, Miguel Gualdron wrote:
> 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.
Does this mean that the link is already brought down and needs to be
redialled, or you can ping it before it actually dies?
> --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.
The point is, that I want the script to be one-shot, and diald should take
care of watching the forced status and calling it periodically.
I could do what you have described with a script managing the ping job,
but I think this 'ip-forced' script would be a nice feature for diald. Of
course I should write it then ;-)
I'm writing about this so maybe someone can write it easier than me.
Anyway, thanks for the replies.
> >you could even dynamically add a cron job.
> >
> >jon
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
