Hi,
just started telnetd manualy … and got the
follwing message:
telnetd &
[1] 765986
telnetd: getpeername: Function not implemented
[1] + Done (1) telnetd
I’m using the big tcpip stack.
What’s wrong?
Hi,
just started telnetd manualy … and got the
follwing message:
[1] 765986
[1] + Done (1) telnetd
I’m using the big tcpip stack.
What’s wrong?
Armin Steinhoff <A-Steinhoff@web_.de> wrote:
: Hi,
: just started telnetd manualy … and got the
: follwing message:
: # telnetd &
: [1] 765986
: # telnetd: getpeername: Function not implemented
: [1] + Done (1) telnetd
: #
: I’m using the big tcpip stack.
: What’s wrong?
You need to let inetd start telnetd. When started
as above, it’s stdin is not a socket. You’re sending
a getpeername message to a manager other than the
stack.
-seanb
Already settled … I’ve got the answer from the
FAQ.
Armin Steinhoff wrote:
Hi,
just started telnetd manualy … and got the
follwing message:telnetd &
[1] 765986
telnetd: getpeername: Function not implemented
[1] + Done (1) telnetd
I’m using the big tcpip stack.
What’s wrong?
Sean Boudreau wrote:
Armin Steinhoff <A-Steinhoff@web_.de> wrote:
: Hi,
: just started telnetd manualy … and got the
: follwing message:: # telnetd &
: [1] 765986
: # telnetd: getpeername: Function not implemented
: [1] + Done (1) telnetd
: #: I’m using the big tcpip stack.
: What’s wrong?
You need to let inetd start telnetd. When started
as above, it’s stdin is not a socket. You’re sending
a getpeername message to a manager other than the
stack.
Thanks … I have created rc.local and start out
of it inetd and NFS.
Is it the right place? (It works so far …)
Armin