Subject: talk oddity?
To: None <port-i386@netbsd.org>
From: Michael G. Schabert <mikeride@prez.org>
List: port-i386
Date: 06/26/1999 16:37:24
Hi i386'ers,

I don't currently run NetBSD on an x86 machine, but I have it running on an
alpha & have had it on my mac68k. I got a buddy of mine to install it on
his k6-2 box, & we just tried to use "talk". First, I logged onto his
machine & noticed that there was no entry for talk in inetd.conf, so I
added it from my alpha:

talk dgram udp wait nobody.tty /usr/bin/talk talk

where the spaces were tabs (although any whitespace should be fine). After
that, I talked my login on his box from my box, & it went through just
fine. But any time we'd try to talk with it orginating on his box, we'd get
this:

[Target machine does not recognize us]


Is that why talk wasn't in the default i386 inetd.conf? Is it somehow
broken just on that port? Would it help for me to have him install ytalk?


Oh, yeah, I also checked his /var/log/messages & saw:

Jun 26 13:39:08 mb1 rshd[193]: getpeername: Socket is not connected
Jun 26 13:45:11 mb1 rshd[238]: getpeername: Socket is not connected
Jun 26 13:45:32 mb1 rshd[246]: getpeername: Socket is not connected
Jun 26 13:46:32 mb1 rshd[256]: getpeername: Socket is not connected
Jun 26 13:47:41 mb1 rshd[299]: getpeername: Socket is not connected
Jun 26 13:48:19 mb1 rshd[325]: getpeername: Socket is not connected
Jun 26 14:00:34 mb1 rshd[381]: getpeername: Socket is not connected
Jun 26 14:35:15 mb1 rshd[427]: getpeername: Socket is not connected
Jun 26 15:42:35 mb1 rshd[605]: getpeername: Socket is not connected
Jun 26 15:54:05 mb1 talkd[681]: recv: Socket operation on non-socket
Jun 26 15:54:12 mb1 last message repeated 20752 times


Any clues greatly appreciated.

lso, please cc: me since I'm not on port-i386 list.

Thanks a lot,
Mike
Bikers don't *DO* taglines.