Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!inquo!news.seinf.abb.se!nooft.abb.no!Norway.EU.net!nntp.uio.no!news.cais.net!newsfeed.internetmci.com!uuneo.neosoft.com!conrads From: conrads@dolphin.neosoft.com (Conrad Sabatier) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Where's my talkd??? Date: 26 Jun 1996 23:59:31 GMT Organization: What? Me, organize? Lines: 54 Message-ID: <4qsit3$cd5@uuneo.neosoft.com> References: <4qefto$de@dolphin.neosoft.com> <31CB1AA0.2D4BB731@lambert.org> <4qk59e$eja@malibu.ts.rz.tu-bs.de> <DtJq42.D9p@ritz.mordor.com> Reply-To: conrads@neosoft.com (Conrad Sabatier) NNTP-Posting-Host: 206.27.165.138 In article <DtJq42.D9p@ritz.mordor.com>, Chris Mauritz <ritz@ritz.mordor.com> wrote: >Martin Butkus (mb@malibu.ts.rz.tu-bs.de) wrote: >: Terry Lambert (terry@lambert.org) wrote: >: : Conrad Sabatier wrote: >: : ] >: : ] This is weird. I have talk, but no talkd, it would seem. Isn't >: : ] this part of the standard distribution? Where should it be >: : ] located? I can't find it anywhere on my system. >: : ] >: : ] Especially strange, since I do have the man page for it. >: >: : /usr/libexec/ntalkd >: >: : (see /etc/inetd.conf -- it knows where all your /etc/services >: : daemons that are "turned on" live...) >: >: Or ask locate(1): >: >: malibu% locate talkd >: /usr/include/protocols/talkd.h >: /usr/libexec/ntalkd >: /usr/share/man/man8/talkd.8.gz > >You also might want to make sure the services are enabled in >/etc/inetd.conf and /etc/services. Sample lines (for BSDI >2.0.1) are included below. They should work for FreeBSD too. > >/etc/inetd.conf: >ntalk dgram udp wait root /usr/libexec/tcpd ntalkd > >/etc/services: >talk 517/udp >ntalk 518/udp > >Note: tcpd is a tcp wrapper program. If you don't have tcp wrappers > installed, the line would look like: > >ntalk dgram udp wait root /usr/libexec/ntalkd ntalkd > >Whether or not you want to run a wrapper is a matter of personal taste. >I personally wouldn't run a publicly accessible machine without one/them. >But that is a whole different can of worms...which I hope I haven't >opened (though it hasn't been discussed here recently *grin*). :-) > >One last comment, are you sure inetd is running? :-) I'm sure >you would have noticed if it wasn't, but it doesn't hurt to ask. Yes, I do have inetd running, but ntalkd wasn't enabled. Thanks to all who replied! -- Conrad Sabatier -- http://www.neosoft.com/~conrads