Marco d'Itri writes: > ----- Forwarded message from Ioannou Ioannis Konstantinos <[EMAIL PROTECTED]> > ----- > > Subject: Bug#308136: pppd seg-faults with nested calls > Reply-To: Ioannou Ioannis Konstantinos <[EMAIL PROTECTED]>, > [EMAIL PROTECTED] > From: Ioannou Ioannis Konstantinos <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > > On May 19 [EMAIL PROTECTED] (Marco d'Itri) wrote : > > > > It seems, using the call option breaks the initialization of the tdb > > > database. > > 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)? Paul. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
