On Sat, 7 Nov 1998, David Shochat wrote:
> Why couldn't you just write a small "wrapper" script that would invoke
> chat and also save the returned value, and then use that script in the
> "connect" parameter of the pppd command line (instead of chat)? I
> haven't tried it, but I don't see why it wouldn't work.
Yes, I think that's part of the solution.
>
> Also, you could use the REPORT keyword in your chat script: wouldn't
> "REPORT BUSY" do it?
Yes. Sorry, I didn't make the problem clear. I would like a script
to dial an indefinite number of times (with pauses) while the remote
end is busy, but only a small number of times if the link
immediately fails for any other reason.
It is possible for the script to specify a unique report file every
time it runs pppd, then pause and grep in that file for "BUSY", but
I hoped there might be a better way. The documented chat exit codes
are not very useful if they can't be seen.
I think running chat in a wrapper script as you suggest, and having
the wrapper script create a flag file if the chat return code
indicates ABORT BUSY, and having the main script look for that file,
is... what I will do... if I can't think of a better way.
> > When pppd is started with a chat script, chat exits with a return
> > value which can refer to an ABORT string in the chat script.
> >
> > I'm looking for a way to find if the remote number was busy when
> > pppd tried to connect. This could be a way, but there seems no way
> > to access the value returned by chat.
> >
>
> -- David
>
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
