On 8/25/2005, "Paul Mackerras" <[EMAIL PROTECTED]> wrote:
>> > It's not supposed to segfault, but I'm not sure if using two times the
>> > call option is supported.
>>
>> Well, this used to work for years. In some laptops I'm using
>> the (old I admit) front-end xisp, and it has this nested-call
>> trick since 199x. Suddendly with the last upgrade on Sarge to
>> 2.4.3 xisp stoped working beacuse of this. I had to downgrade to 2.4.2
>> before I had time to debug and realise that this is the problem.
>>
>> For sure the manual page does not says that it is not allowed.
>
>There should be no problem in using the call option more than once or
>recursively. How exactly does using the call option break the
>initialization of the tdb database (and what does breaking the
>initialization mean exactly)?
>
I'm not sure what is the problem with the tdb database under Debian, I
have noticed this "warning" since I switched from Redhat to Debian,
more than one year now, but never broke anything obvious.
What I said is maybe not relevant with the "tdb problem" : with 2.4.3
you can not use nested 'call' options.
The example with xisp goes like this: the program calls (let say)
/etc/ppp/peers/xisp_modem which normally inside,
at the bottom, has a line :
call xisp_dialer
i.e. a nested call. This used to work from late '90s up to 2.4.2.
With 2.4.3 (at least under Sarge) this is seg-faults.
Rgrds
iik1
