On Sun, 18 Apr 1999, Mike Jagdis wrote:
> On Tue, 13 Apr 1999, Ed Doolittle wrote:
> > On Mon, 12 Apr 1999, Mike Jagdis wrote:
>>> If you mean /etc/ppp/options had connect options and the like
>>> in it then this is *WRONG*. /etc/ppp/options is for *global*
>>> settings. If some distribution actually puts the full options
>>> for a specific link in there you might as well send the CD
>>> back for a refund and try something else. Surely no one is
>>> being *paid* to be that dumb?!?
>> The auth option belongs in /etc/ppp/options. Furthermore, most of
>> the other bad options would be considered global options by most
>> people ... modem, crtscts, etc. Connect options do belong in
>> /etc/ppp/peers/* , which is exactly where Debian places them.
> Whoa... I was with you until that point. I can't find any
> mention of /etc/ppp/peers in the nondistributionized diald
> or pppd (as of 2.3.5) archives.
In 2.3.4 /etc/ppp/peers is mentioned in the manual page, in
pppd/pathnames.h, and in pppd/options.c (and wherever else _PATH_PEERFILES
is mentioned). Have things changed in 2.3.5?
/etc/ppp/peers/ is just where pppd looks for options files given with
the call option. So if I execute "pppd call netcom" it loads the
global options file /etc/ppp/options and then the options file
/etc/ppp/peers/netcom . I'm sure every distribution does something
like this. Just substitute the distribution's _PATH_PEERFILES for
/etc/ppp/peers . But I am surprised that it has changed.
In any case, I was saying that connect scripts don't belong in
/etc/ppp/options, they belong in per-peer option files. Clearly. I
know you agree with me about that. The problem is that some options
that diald doesn't like, such as modem, lock, crtscts, etc., end up in
the global options file. We can ask everyone who uses diald to
comment out those options in the global file and put them into their
peer options files (perhaps by some kind of include mechanism) which
is a bit of a pain, and a support problem as we have been seeing. Or
we can try to find some other way of handling it.
Since we are running pppd as root we should be able to override the
global defaults. I suggest we encourage the pppd developers to add a
"noglobaloptions" command line option which can be used only by root.
Then diald can start pppd with a clean slate, and any options that are
required can be invoked through the diald options file.
Ed
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
