-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
well... it is strange... after playing a bit with ports talk and ntalk... discovered that talk works only with "talk user@localhost" and not "talk user" still... the ytalk is still does not work. I even moved the talk service to port 518 and ntalk to 517.... still doesn't work... on RH9 all was ok.
... and indeed it doesn't especially need talk because in.talkd is on 517 and ntalkd is on 518... and talk goes to 518.
what about ytalk? it was useful...
Tim Sheets wrote:
| hmmmm...I just tried this and had no problems. To start, I didn't | have the talk-server installed. | | <snip of history> 994 up2date talk-server 995 chkconfig --list | 996 chkconfig ntalk on 997 service xinetd restart <end of snip> | | Then I opened a couple of sessions and typed 'talk <username>' and | everything worked as expected. One thing that I noticed when | trying to get this to work on RH9 is that you only have to turn on | ntalk, not talk itself. But, the command is still talk. | | xinetd based services: chargen-udp: off rsync: off chargen: | off daytime-udp: off daytime: off echo-udp: off | echo: off services: off time: off time-udp: off | cups-lpd: off sgi_fam: on ntalk: on talk: off | | | Also, I don't think the firewall would have any effect on talking | to someone on the same host. I know I didn't make any special | modifications, but then again, maybe (probably) I am not as secure | as some others might be. | | Good Luck. | | Tim | | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAByWsf6910gYCyYMRAp8QAJ47WAyYjN1KMsBWsyN32N+wDOazygCeMu2P pQsf2SFQmAU8OF40MORqC7A= =m9vY -----END PGP SIGNATURE-----
