All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: linux-ppp@vger.kernel.org
Subject: options in plugins?
Date: Sun, 10 Jul 2005 17:10:18 +0000	[thread overview]
Message-ID: <87wtny1tad.fsf@stark.xeocode.com> (raw)


I'm not sure if development on pppd is still active. It seems there are dozens
of patches floating around and no upstream releases coming. Is it? Is this
still the list to reach the upstream maintainers?

My question is whether there's a way to add options in a plugin. It seems the
options list is a static array in plugins.c and plugins are loaded using
dlsym. So unless I've missed some piece of infrastructure there isn't.

This is really unfortunate. My ultimate goal is to make the timeouts and
retries in pppoe configurable just as they are for LCP. Currently they're set
to 5s with unbounded exponential backoff and a max of 3 retries. That makes
any temporary outage of even about 30s result in a complete failure.

I've hacked my personal copy to just retry every 5s forever but in an ideal
world there would be a pppoe-restart and pppoe-maxfail just like lcp-restart
and maxfail that could be set in the options or peers files.

But I don't see any reasonable way to do that without writing a lot of code.
Nor am I clear whether such a patch would eventually get released. There's not
much point in writing it just for myself -- I have my personal version hacked
up for my use already. If development is dead then there's not much point in
fixing this problem so generally.

-- 
greg


             reply	other threads:[~2005-07-10 17:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-10 17:10 Greg Stark [this message]
2005-07-10 20:30 ` options in plugins? Grant Coady
2005-07-10 22:41 ` David Ananian-Cooper
2005-07-11  1:20 ` Paul Mackerras
2005-07-11 10:52 ` 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=87wtny1tad.fsf@stark.xeocode.com \
    --to=gsstark@mit.edu \
    --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.