All of lore.kernel.org
 help / color / mirror / Atom feed
From: walter harms <wharms@bfs.de>
To: linux-ppp@vger.kernel.org
Subject: Re: Control pppd behaviour
Date: Thu, 11 Feb 2010 09:03:01 +0000	[thread overview]
Message-ID: <4B73C7C5.2050603@bfs.de> (raw)
In-Reply-To: <27543592.post@talk.nabble.com>



Hashmat Khan schrieb:
> Hello,
> 
> I understand that pppd uses parameters from different files such as those
> located in /etc/ppp directory to control its behaviours on failures etc.
> 
> I wanted to know if its possible to say for example implement a different
> retry algorithm(user defined). Is this possible without modifying code ?
> 


What do you try "to retry" ? when one provider is down you can easy switch to others.
like this (not working) example:

#!/bin/sh
for PROV in prov1 prov2 prov2
do
	pppd call $PROV
	if [ everythink_works ]
		exit 0
done

exit 1


re,
 wh





  reply	other threads:[~2010-02-11  9:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11  8:10 Control pppd behaviour Hashmat Khan
2010-02-11  9:03 ` walter harms [this message]
2010-02-11 12:05 ` Ashmath Khan
2010-02-11 13:18 ` James Carlson
2010-02-11 13:39 ` James Carlson
2010-02-11 13:43 ` Ashmath Khan
2010-02-11 13:49 ` Ashmath Khan
2010-02-11 14:41 ` James Carlson
2010-02-11 14:45 ` James Carlson
2010-02-11 14:51 ` Ashmath Khan
2010-02-11 14:51 ` Ashmath Khan
2010-02-11 14:58 ` James Carlson
2010-02-11 14:59 ` Ashmath Khan
2010-02-11 15:15 ` Ashmath Khan
2010-02-11 15:45 ` James Carlson
2010-02-11 16:50 ` Ashmath Khan
2010-02-11 17:01 ` James Carlson
2010-02-11 17:44 ` James Carlson
2010-02-11 17:48 ` Ashmath Khan
2010-02-11 17:52 ` Charlie Brady
2010-02-12  2:24 ` Ashmath Khan
2010-02-12  8:04 ` James Chapman
2010-02-12 12:55 ` James Carlson
2010-02-12 14:20 ` Ashmath Khan
2010-02-12 14:32 ` James Carlson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B73C7C5.2050603@bfs.de \
    --to=wharms@bfs.de \
    --cc=linux-ppp@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.