I run into this problem when running in.talkd daemons between Debian 8.5
and Fedora 24. I'm letting everyone know about how I could make the two
work even though not one of the involved machined was an Ubuntu one,
because I guess the issue other people experienced years ago could be
caused by the s
Hmm; this bug is a bit confusing; On quantal I've got ytalk(3.3.0-5) to
work with talkd (0.17-15) (using openbsd-inetd)
However, while the text of the report talks about using apt-get source talkd,
the package it is associated with is inetutils,
and inetutils has it's own talkd, inetutils-talkd.
I've duplicated the bug in 8.10. The only way I could get talk/ytalk to
work is by making these changes - modifying inetd.conf to use udp4 and
adding user nobody to group tty.
--
talkd does not work
https://bugs.launchpad.net/bugs/232051
You received this bug notification because you are a member
Yeah. inetd.conf, "udp"s should be "udp4"s or an IPV6 connection
is being used I think. Also, I found when running as "nobody" (since
nobody.tty doesn't work), that ytalk would return "[EMAIL PROTECTED]
refusing messages". Running as "root" I get a ytalk request properly.
I suppose this is
So, I pulled the source, commented out the sanity checks that force
talkd to say "talkd[13554]: recvfrom: bogus address length". WIth this
commented out it said "bogus address family". With *this* commented
out, it logs lines such as "Oct 3 23:44:56 voltron talkd[15391]:
::a00:205:0:0 (0.0.
Ran into this problem today, to my frustration! That's at least one
other user who still cares about talk/talkd.
--
talkd does not work
https://bugs.launchpad.net/bugs/232051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
