just for the record, i figured out what was wrong with ytalk. btw, thanks
to all that replied (that being zero of you). ;p
starting with RH/MDK 6.0 (which have newer versions of ytalk), you
*cannot* use ytalk if the "talkd" daemon is enabled in /etc/inetd.conf.
it needs to look like so:
#talk dgram udp wait root /usr/sbin/tcpd in.talkd
ntalk dgram udp wait root /usr/sbin/tcpd in.ntalkd
technically, in.talkd and in.ntalkd are the same daemon. for some reason,
ytalk freaks if both are enabled, yet reports it can't find a talk daemon
when only talkd is enabled...go figure.
i thought we had tried all the possible combinations of daemons, but we
must have forgot to reload inet once. doh...anyway...
so, that's the scoop. hope this will help someone out later in the
archives.
cameron
ps - roger, i couldn't reach the ytalk homepage to see if a fix has been
made or if the bug has been reported yet. thanks
On Sat, 28 Aug 1999, Hrothgar wrote:
:[1] summary:
:
: ytalk does not work.
:
:
:[2] full description:
:
: ytalk hangs at the "Waiting for connection..." stage (on both clients).
:to end the session, you have to suspend (^Z) and then `kill -9` the
:process.
:
:
:[3] versions:
:
: Mandrake 6.0 (Venus)
: ytalk 3.1-3
: ytalk 3.1.1 [same result; went back to 3.1-3 rpm for support reasons]
:
:
:[4] /etc/inetd.conf:
:
: talk dgram udp wait root /usr/sbin/tcpd in.talkd
: ntalk dgram udp wait root /usr/sbin/tcpd in.ntalkd
: dtalk stream tcp wait nobody /usr/sbin/tcpd in.dtalkd
: # enabled dtalk just for good measure
:
:
:[5] /etc/services:
:
: talk 517/udp
: ntalk 518/udp
:
:
:[6] other info:
:
: we primarily need ytalk to work on the localhost; ytalk with a
:remote host hardly ever happens (i'm speaking past tense here about our
:prior setup with RH5.2).
:
: /usr/local/etc/ytalkrc is in place
:
:
:can you reproduce this problem on your box(es)? it's almost imperative
:that we get this working. any help would be greatly appreciated. TIA
:
:cameron
:
: [ How's my programming? Call 1-800-DEV-NULL ]
:
:
