Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If you make changes to inetd.conf you will need to either reboot, restart the inetd or send the inetd process a HUP signal to tell it to reread the inetd.conf.
Thankx for the replies..
i tried the things that you told me...
I do not have a inetd.conf instead "xinetd.conf" . i guess its equivelent to the former.
I saw the contents of the xinetd.conf . The dir. xinetd.d was included in that file.
In that dir. there is a talk file which has some parameters for talk.
i made disable=no , all other parameters have the default values.
the wait=yes, user=nobody, socket_type=dgram, server=/usr/sbin/in.talkd
then i restarted the linux server,, but still i have the same problem and the same error message.
Did I do something wrong ? is there anything more to do ?
This is simply driving me up the proverbial tree :-)
Has anyone given a working solution to this problem? I would be very grateful if someone could indicate or hint at how to start in.talkd (or in.ntalkd) on a Redhat 9.0 system WITHOUT getting a "Socket operation on non-socket" error.
2. Use vi or your favorite text ditor as root to edit the files,
"talk" and "ntalk" Change the lines, "disable = yes" to "disable = no" in both files
3. /etc/init.d/xinetd restart
Done.
Should work to all local users, you may experience issues if trying to connect to remote computer or trying to use talk over the local network or the internet for that matter. Good luck'
i'm having the same problems.
i'm running redhat 9
all the /etc/xinnet.d/talk ntalk ktalk have the disable=no
i have restarted xinetd service
i am on a single switch from
i can talk on local account
yet not over the network ie. talk crickett@192.168.0.2 from 192.168.0.3
suggestions
there seems to be no howto;s out there that discuss this
If you guys are getting this to work locally, then it's another network configuration that are preventing this to work over the "network".
Does it work on the internal "network"? and localhost? If yes and not on the "internet". Then you consider most likely a firewall is blocking the port this service uses? Or the firewall on the host your trying to talk to has this port closed also. See what I getting at here guys?
ok this is located on a local network
ie computers are both connected into a switch
port 517 518 are closed
this is the issue
i'm needing to open these ports
yet i understand that xinetd manages the ports and services and keeps them closed until needed. so do i open the ports to allow the talkd? should i goto inetd instead of xinetd?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.