From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Control pppd behaviour
Date: Fri, 12 Feb 2010 14:32:58 +0000 [thread overview]
Message-ID: <4B75669A.8010904@workingcode.com> (raw)
In-Reply-To: <27543592.post@talk.nabble.com>
On 02/12/10 09:08, Ashmath Khan wrote:
> Thanks James.
>
> I am thinking of this:
> maxfail 1
> persist # or demad
>
> Keeping these two options will make pppd exit and my app can later
> control starting pppd later depending on the exit code and the
> algorithm.
> Sometimes we also use demand instead of persist depending on the user
> configuration from UI.
>
> What do you think ?
Do what you want, but I recommend omitting both options based on your
previously stated goal of having pppd exit on failure.
If you do use "demand" with your current configuration, I recommend
including "nopersist" in order to get the failure semantics desired.
I'm not sure I see how "demand" really fits in here, but you haven't
revealed enough information to give better advice. And I'm not going to
continue playing 20 questions to get it. :-/
--
James Carlson 42.703N 71.076W <carlsonj@workingcode.com>
prev parent reply other threads:[~2010-02-12 14:32 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
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 [this message]
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=4B75669A.8010904@workingcode.com \
--to=carlsonj@workingcode.com \
--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.