Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > macOS > The talk command in OS X

The talk command in OS X
Thread Tools
CharlesS
Posting Junkie
Join Date: Dec 2000
Status: Offline
Reply With Quote
Jul 15, 2001, 06:33 PM
 
Why doesn't the talk command work out of the box? I tried using it to talk to various machines and it never worked. I uncommented the reference to ntalkd in inetd.conf, with no change. I downloaded the source for the FreeBSD versions of talk and talkd, compiled those, and they worked just fine. So why doesn't the version included with Darwin work?

[ 07-15-2001: Message edited by: CharlesS ]

Ticking sound coming from a .pkg package? Don't let the .bom go off! Inspect it first with Pacifist. Macworld - five mice!
     
krove
Mac Elite
Join Date: Jul 2000
Location: Washington, DC
Status: Offline
Reply With Quote
Jul 16, 2001, 05:07 AM
 
How about some instructions on compiling talk and talkd?

How did it come to this? Goodbye PowerPC. | sensory output
     
CharlesS  (op)
Posting Junkie
Join Date: Dec 2000
Status: Offline
Reply With Quote
Jul 16, 2001, 05:40 AM
 
Okay, but you're going to be disappointed if you expect UNIX-guru stuff, because I don't know much more than you do about it

All I did was open Project Builder, created a new project of type "Standard Tool," deleted the main.c file it already had in there, dragged the source files for talk into the project, hit the build button, and crossed my fingers. In the case of talkd, I had to get an include file from elsewhere on the FreeBSD site before it would compile, but once I had all the files, it worked great.

Now, if only someone knew why the version of talk included with Darwin doesn't work...

Ticking sound coming from a .pkg package? Don't let the .bom go off! Inspect it first with Pacifist. Macworld - five mice!
     
ppmax
Dedicated MacNNer
Join Date: Nov 1999
Status: Offline
Reply With Quote
Jul 21, 2001, 10:08 PM
 
FYI--it does work out of the box. you just have to do one more step.

for talk to work both users have to make sure and do this:

from the CLI type "mesg y"

remember: both users have to do this.
     
CharlesS  (op)
Posting Junkie
Join Date: Dec 2000
Status: Offline
Reply With Quote
Jul 22, 2001, 05:49 PM
 
Originally posted by ppmax:
<STRONG>FYI--it does work out of the box. you just have to do one more step.

for talk to work both users have to make sure and do this:

from the CLI type "mesg y"

remember: both users have to do this.</STRONG>
Actually, mesg y is the first thing I tried. It didn't work.

And I know the machines I was trying to talk to were working, because once I compiled the FreeBSD talk and tried it, it worked with them.

I realize now that I forgot to post the error that talk was giving me when I tried it out of the box. It gave:

[No connection yet]
[Checking for invitation on caller's machine]

The last message kept repeating over and over, and it never connected. Once I compiled and used the FreeBSD version of talk, it worked perfectly.

Thanks for the response, though.

Ticking sound coming from a .pkg package? Don't let the .bom go off! Inspect it first with Pacifist. Macworld - five mice!
     
Pismo Of Ages
Junior Member
Join Date: Mar 2001
Location: Right behind you...
Status: Offline
Reply With Quote
Jul 29, 2001, 12:35 PM
 
there must be some way to enable it, anyone?
     
Pismo Of Ages
Junior Member
Join Date: Mar 2001
Location: Right behind you...
Status: Offline
Reply With Quote
Aug 21, 2001, 09:16 PM
 
I was talking to one of Apple's UNIX programmers today at Cupertino and we spent 15 minutes figuring it out, and here are the steps...

1. Edit "/etc/inetd.conf" to enable (uncomment) ntalkd

2. For each user who wants to talk, they need to:

a) "login" as a terminal (su won't work)

b) setenv TERM vt100

(possibly unsetenv TERMCAP)

c) mesg y

Test using "write"

yah =)
your welcome

-Jon
     
   
 
Forum Links
Forum 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 On
HTML code is Off
Top
Privacy Policy
All times are GMT -4. The time now is 09:41 AM.
All contents of these forums © 1995-2017 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.8 © 2000-2017, Jelsoft Enterprises Ltd.,