LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 10-24-2011, 12:31 PM   #1
kris108
Member
 
Registered: Sep 2009
Distribution: Slackware
Posts: 32

Rep: Reputation: 2
How to start the talk daemon?


I would like to use ytalk and set in /etc/inittab:
Code:
talk    dgram   udp     wait    root    /usr/sbin/tcpd  in.talkd
ntalk   dgram   udp     wait    root    /usr/sbin/tcpd  in.talkd
I can contact an other (different linux) box on the internal network, but attempts contacting this slackware box fails as "no talk daemon is running". I did not figure out what else is to be set.

Addendum:
I must have missed something, the talk daemon was running. It is still unusable, than the reply now is that the user is "not logged in" (naturally is logged in).

Last edited by kris108; 10-24-2011 at 10:16 PM.
 
Old 10-25-2011, 07:53 AM   #2
wildwizard
Member
 
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 755

Rep: Reputation: 226Reputation: 226Reputation: 226
Just did some quick and dirty testing here

ytalk works and uses the talk line in inetd.conf
talk gives the error you describe and uses the second ntalk line

Make sure your using ytalk on both ends
 
Old 10-25-2011, 02:00 PM   #3
kris108
Member
 
Registered: Sep 2009
Distribution: Slackware
Posts: 32

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by wildwizard View Post
Make sure your using ytalk on both ends
Yes, ytalk was used on both boxes, these have fix IP addresses on the internal network. I can ring the other linux from the Slackware box but can not "call back".

Anyway, thank you for your efforts.
 
Old 10-25-2011, 02:52 PM   #4
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,447

Rep: Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875
in.talkd runs under inetd, so you should check /etc/hosts.allow too for allowing the boxes to talk each other
Code:
in.talkd: 192.168.1.2
just put in the ip/name(s) of the other box(es) ("man 5 hosts_access")
 
Old 10-26-2011, 09:57 AM   #5
kris108
Member
 
Registered: Sep 2009
Distribution: Slackware
Posts: 32

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by ponce View Post
in.talkd runs under inetd, so you should check /etc/hosts.allow too for allowing the boxes to talk each other
Code:
in.talkd: 192.168.1.2
just put in the ip/name(s) of the other box(es) ("man 5 hosts_access")
Set, the result is the same. The port 518/udp is open, I can ring the oder box (not Slackware) but can not call back as the user is reported to be "not logged in". If I try to call the router, than ytalk correctly reports that no talk daemon is running at that IP. So the talk daemon is running, the port is open and now allowed in /etc/hosts.allow. I guess I give up and look for something else.

I did like the idea that no server is required by ytalk and don't really intend to use Google Talk which loads a list of my "Contacts" and notifies them all that I am online. I find ytalk would provide me with more freedom

It is regrettable that ytalk seems not to be really supported anymore. (The next question would been: how to get a notification about an incoming call in an X-environment /there was'nt any on the oder box, I had to open a terminal waiting for the ringing

Best regards

Last edited by kris108; 10-26-2011 at 10:03 AM.
 
Old 10-26-2011, 11:18 AM   #6
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,447

Rep: Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875
you can specify the tty on the talk command line, so you just need to know the tty on which your user has a running shell (let him run the "tty" command to find it, works also under X).
 
Old 10-26-2011, 12:22 PM   #7
kris108
Member
 
Registered: Sep 2009
Distribution: Slackware
Posts: 32

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by ponce View Post
you can specify the tty on the talk command line, so you just need to know the tty on which your user has a running shell (let him run the "tty" command to find it, works also under X).
Did not solve the issue. The ringing is received on the other box (not Slack) even without specifying the tty (both were on "0").

Meanwhile I searched the net but did only find "lan messengers" which is not the same as they can not be used over the internet.
 
Old 10-26-2011, 12:33 PM   #8
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,447

Rep: Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875
Quote:
Originally Posted by kris108 View Post
(The next question would been: how to get a notification about an incoming call in an X-environment /there was'nt any on the oder box, I had to open a terminal waiting for the ringing
sorry if I wasn't clear, that was an answer to this
you have to open a terminal under X, because talk rings on ttys.

Last edited by ponce; 10-26-2011 at 12:36 PM.
 
Old 10-26-2011, 12:53 PM   #9
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,447

Rep: Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875
If you want something to use through internet maybe you have to move away from talk (I think it's not safe for internet use) and use pidgin (in stock slackware) with some protocol (jabber or whatever) you don't already use (so no bothering for friends there).
 
Old 10-26-2011, 01:07 PM   #10
kris108
Member
 
Registered: Sep 2009
Distribution: Slackware
Posts: 32

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by ponce View Post
If you want something to use through internet maybe you have to move away from talk (I think it's not safe for internet use) and use pidgin (in stock slackware) with some protocol (jabber or whatever) you don't already use (so no bothering for friends there).
Yes, "not safe" as clear text is sent, that is of no concern to me. I would'nt do any serious communication through the internet. If something is that important I tell/bring it personally (not on phone, email etc My concern with Pidgin et al is that they do not respect my privacy as I would like to have it. I register by a provider which keeps track on my contacts, loads them on a list, reports me online etc. You know it all. I instinctively stay away from those services. ytalk would be fine if it would work on Slackware (works on my girlfriends box with a different linux and did not find the difference, I am lost on that system, too
 
Old 10-26-2011, 02:31 PM   #11
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,447

Rep: Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875Reputation: 875
ngircd?
you can refeer here for an easy configuration and to slackbuilds.org for the build script.

Last edited by ponce; 10-26-2011 at 02:41 PM.
 
1 members found this post helpful.
Old 10-26-2011, 03:05 PM   #12
kris108
Member
 
Registered: Sep 2009
Distribution: Slackware
Posts: 32

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by ponce View Post
ngircd?
you can refeer here for an easy configuration and to slackbuilds.org for the build script.
Yes, I already considered. I am not a big fan of IRC but that might be the way to go.

By the way: the router/server is openwrt and ngircd is already in the repository. (Had a Slackware server for approx 6 years running but the CISCO consumes about only 5W and have an acceptable system - though with compromises - using openwrt)

Many thanks for your advices!
 
Old 01-31-2013, 12:27 AM   #13
dchmelik
Member
 
Registered: Nov 2008
Location: Washington state, USA
Distribution: BSD, GNU/Linux (Slackware, etc.,) openSolaris
Posts: 197

Rep: Reputation: 21
Are you trying it on the terminal only? If not, you might have to have $DISPLAY set in /etc/profile or ~/.bashrc to the one X runs as, .i.e., do 'ps ax|grep X' and right after you should see something like ':0'. Then you have to 'export DISPLAY=:0' (or the number right after 'X') in profile or bashrc. I am not sure I was getting the pop-up messages until I tried this.

You also need to go to a shell and type 'mesg y' for every user you want to be able to receive messages.

Last edited by dchmelik; 01-31-2013 at 12:32 AM.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Using the talk daemon kaplan71 Linux - General 1 05-22-2010 06:47 AM
talk daemon running but not accepting connections ikjeft01 Red Hat 2 03-29-2010 09:19 PM
Bash script to verify the daemon is working if not, start the daemon kishoreru Linux - Newbie 7 09-23-2009 04:29 AM
talk talk daemon configuration ananthkrk Red Hat 1 10-16-2004 11:45 AM
Can't run talk daemon ust Linux - General 3 05-24-2004 04:07 PM


All times are GMT -5. The time now is 07:59 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration