baldu...@units.it schrieb:
>
> are you sure that xinetd is picking libtirpc up?
>
> pmap_{set,unset} are in libtirpc and in order to force the xinetd build
> process to link in libtirpc I had to:
>
> export LDFLAGS="-ltirpc"
that's it. now libtirpc
Further to my last on popper/xinetd not working from another client on the
same subnet, I rebuilt qpopper with debugging support. Here's an extract
from sys.log when the attempt to connect from another client occurs:
Apr 26 13:50:08 wiggle_butt xinetd[16303]: Reading included configuration
Sigh. I like linux, but it sure is a pain in the ass to get working
sometimes.
I have the qpopper popper program running under xinetd. When I try to access
it from across my subnet via telnet I get rejected on the client side and a
message prints out on the lfs system console to the effect that