LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   How to talk/ytalk in slackware? (http://www.linuxquestions.org/questions/slackware-14/how-to-talk-ytalk-in-slackware-4175469583/)

narke 07-14-2013 05:20 AM

How to talk/ytalk in slackware?
 
Hi, Group

I have not figure out how to make talk/ytalk work on my slack box. I've already enabled in.talkd daemon in my inetnd.conf file. But it just still does not work. I test it in the same computer. The command line is:

~user-b $ talk user-a (in one terminal window)
~user-a $ talk user-b (in another terminal window)

the talk program seems complains that peer user is not logged in.

Can anyone has a successful experience? Thanks.

-
woody

eternauta2001 07-14-2013 07:26 AM

Add in /etc/hosts.allow

talkd: ALL

Reload inetd with

# killall -HUP inetd

narke 07-14-2013 09:12 AM

Quote:

Originally Posted by eternauta2001 (Post 4990080)
Add in /etc/hosts.allow

talkd: ALL

Reload inetd with

# killall -HUP inetd

The result is the same. In one end, it says "trying to connect to your party's daemon", in the other end, it says: "Waiting for your party respond"

I think even without "talkd: ALL", my previous hosts.allow should already allow the talk traffic, since it has "ALL: 192.168.0.0/255.255.0.0"

mancha 07-14-2013 10:23 AM

If you're using slackware's talk(1) you are using the ntalk protocol (udp/518).
Try enabling a listening daemon in inted.conf

Code:

ntalk  dgram  udp    wait    root    /usr/sbin/tcpd  in.talkd
and restarting inetd via

Code:

$ killall -HUP inetd

eternauta2001 07-14-2013 10:26 AM

Sorry, is in.talkd in /etc/hosts.allow no talkd...

Code:

in.talkd: 192.168.0.0/255.255.255.0
Restart inetd:

Code:

# killall -HUP inetd
and allow write access in your terminal:

Code:

$ mesg yes
This works for me.

narke 07-22-2013 11:25 AM

Quote:

Originally Posted by eternauta2001 (Post 4990150)
Sorry, is in.talkd in /etc/hosts.allow no talkd...

Code:

in.talkd: 192.168.0.0/255.255.255.0
Restart inetd:

Code:

# killall -HUP inetd
and allow write access in your terminal:

Code:

$ mesg yes
This works for me.

Followed this method, I got target machine does not recognize us ...


All times are GMT -5. The time now is 08:55 PM.