Hi.
I've recently been having difficulties using the ytalk program (ytalk 3.1)
. I'm running a Slackware 3.6 system, and talk used to work flawlessly...
when trying to use ytalk, it would not find a talk daemon, executing
in.talkd as root would temporarily fix the problem, but any subsequent
uses of ytalk wouldn't work without root's intervention by executing the
daemon again. Looking in /etc/inetd.conf, I saw two talk related lines...
one for ntalk (Which was uncommented) and one for talk (Which was
commented)...I did the switch, and reset inetd. Voila, ytalk worked
without intervention...
I thought all was good until a future session (couple system reboots
later) when I discovered that talk nor ytalk won't work at all... no talk
daemon found.
I portscanned myself, and discovered I had a port 715 open...looking in
/etc/services, I saw that port 517 was the one I wanted... could the talk
daemon be improperly setup on the wrong port? (and how would one change
it??)
Also, after fiddling with resetting inetd on either the ntalk or talk
line, I COULD get talk/ytalk to work ONCE. Then I did a:
ps aux
and I saw several screens of in.talkd's... killing them all, I tried
again, and sure enough, six in.talkd's would be created everytime I tried
using talk or ytalk (fail or success)...exiting the program didn't change
much, they still remained running. Looking in my syslog reveals messages
of the following:
... many more connect from's above ...
Apr 11 19:52:08 aquarius in.talkd[1862]: connect from 192.168.12.1
Apr 11 19:52:54 aquarius in.talkd[1865]: connect from 192.168.12.1
Apr 11 19:53:21 aquarius in.talkd[1873]: connect from 192.168.12.1
Apr 11 19:53:28 aquarius in.talkd[1874]: connect from 192.168.12.1
Apr 11 19:53:31 aquarius talkd[1890]: recv: Socket operation on non-socket
Apr 11 19:53:36 aquarius last message repeated 3880 times
Apr 11 19:53:37 aquarius in.talkd[1875]: connect from 192.168.12.1
Apr 11 19:53:36 aquarius talkd[1890]: recv: Socket operation on non-socket
Apr 11 19:53:41 aquarius last message repeated 3390 times
Apr 11 19:53:41 aquarius in.talkd[1876]: connect from 192.168.12.1
Apr 11 19:53:41 aquarius talkd[1890]: recv: Socket operation on non-socket
Apr 11 19:53:41 aquarius last message repeated 13 times
Apr 11 19:53:41 aquarius in.talkd[1877]: connect from 192.168.12.1
Apr 11 19:53:41 aquarius talkd[1890]: recv: Socket operation on non-socket
Apr 11 19:53:58 aquarius last message repeated 14303 times
If anyone can shed any light on this problem I'd greatly appreciate it.
I've been combing over man pages and have come up with nothing.. I am not
ruling much out... it IS a freshly compiled ytalk binary.. but I've
recently had a bout of improper reboots (faulty video card-- right smack
in the middle of ytalk working and not working)...had fsck errors on boot
which I have fixed, but who knows if any damage remains... configuration
problems may also be a cause... I'm open to suggestions.
Thanks in advance.
p.s. I'm not subscribed to linux-newbie, so if any replies could be Cc:'ed
to me I'd appreciate it.
------*-*-*----------------------------------------<< 207.127.232.247 >>--
* * * Atari 8-bit! Battlestar: Galactica * DESCENT * 486
* * * 400/800/XL/XE Star Wars * SeaQuest * Voltron * Summer
* * * * * 2600/5200/7800 Star Trek * WarCraft II * SPARCstation 2
** * **
--Slackware-3.6-------! ! ! ! L I N U X ! ! ! !--------------2.2.5--
