On Sun, 28 Feb 1999, Giulio wrote:
> In both cases I'm asked if I want to remove a syscall from the tcpwrapper lib, even
>if I
> specified in the Makefile I don't want to use tcpwrappers.
That's because the presence of setenv.o in the tcp_wrappers libwrap.a
is a *serious* bug that affects anything linked against it. In particular
any program linked with the setenv.o in libwrap.a and libc6 will
crash and burn if it calls setenv(). If you let the fixwrapper script
get rid of it it will shut up. If not you get to live with the
complaints and consequences...
> In both cases the connections dies as soon as it is estabilished. diald.conf is the
>same
> of 0.98.2.
If you didn't let fixwrappers fix your libwrap.a and enable tcp
wrappers diald will *always* fail at this point since it calls
setenv(). If you don't compile with tcp wrappers...
> It seems pppd fails to start (status 256). I think that maybe this is due to the new
>pppd
> option "nodefaultroute", that diald inserts automatically.
> I have pppd2.2 which understands "-defaultroute"; I know that now pppd is replacing
>all
> "-" with "no", but "man pppd" of 2.2 doesn't show "nodefaultroute".
...bum :-). The 2.3.5 pppd understands both "no..." and "-..."
but 2.2 only understands "-...". Ah well... :-(
You can edit ppp.c and change the one occurance of "nodefaultroute"
to "-defaultroute".
Mike
--
.----------------------------------------------------------------------.
| Mike Jagdis | Internet: [EMAIL PROTECTED] |
| 280, Silverdale Road, Earley, | Voice: +44 118 926 6996 |
| Reading RG6 7NU ENGLAND | Work: +44 118 989 0403 |
`----------------------------------------------------------------------'
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
