On 19.02.2020. 22:08, [email protected] wrote:
I've set my hostname to point to 127.0.0.1 and I still receive the
same error. I tried with and without the domain information.
Is there a log for talkd or inetd? I've attempted to use the -d
flag for inetd however I receive no error messages or warnings.
Ben Raskin.
I haven't used talk in decades (literally), but here is an interesting comment
from /etc/hosts on the system I am currently logged in (a Slackware Linux):
--------------------
#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server. Just add the names, addresses
# and any aliases to this file...
#
# By the way, Arnt Gulbrandsen <[email protected]> says that 127.0.0.1
# should NEVER be named with the name of the machine. It causes problems
# for some (stupid) programs, irc and reputedly talk. :^)
#
# For loopbacking.
127.0.0.1 localhost
172.30.1.10 myhost.mydomain.lan myhost
--------------------
So it seems that talk had always been picky about host name resolution.
Appart from setting your address and host and domain names in /etc/hosts, do you
have a "lookup file bind" line in /etc/resolv.conf ? If you don't, it defaults
to "lookup bind file", so it will query DNS first, and then look into
/etc/hosts. There is a possibility this too can confuse talk.
Best regards,
Zeljko Jovanovic
