Re: Control pppd behaviour

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Audio Users]     [Linux for Hams]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Fedora Users]

  Powered by Linux