Very Computer

Dec 16 12:00:30 svfsun inetd[130]: 100083[29809] from 147.232.23.6 32907
Dec 16 12:00:30 svfsun rpc.ttdbserverd[29809]: refused connect from unknown
Dec 16 12:00:36 svfsun rpc.ttdbserverd[29810]: warning: can't get client address : Transport endpoint is not connected
Dec 16 12:00:36 svfsun inetd[130]: 100083[29810] from 147.232.23.6 32907
Dec 16 12:00:36 svfsun rpc.ttdbserverd[29810]: refused connect from unknown
Dec 16 12:00:42 svfsun rpc.ttdbserverd[29811]: warning: can't get client address : Transport endpoint is not connected

etc etc
what's wrong here, is it impossible to run ttdbserverd through inetd ?
--
 Matus "fantomas" Uhlar, network manager at faculty of civil engineering
 of Technical University in Kosice, Slovakia

I don't think there's a TLI way or even a Socket way to "peek" at the
address that is connecting without doing a destructive "accept".

Once one connection has been let in, rpc.ttdbserverd will do all the
"accept"s itself.

You cannot "tcp wrap" "wait" connection oriented daemons.  I'll file
a bug on the misleading inetd log messages.

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.