[KLUG Members] Talk
Peter Buxton
members@kalamazoolinux.org
Wed, 28 May 2003 20:15:46 -0400
On Wed, May 28, 2003 at 08:10:22AM -0400, Jeremy Leonard was only escaped
alone to tell thee:
> I tried starting it from the bash prompt. The server daemon I mean.
> /usr/sbin/in.talkd
Did you do it as root? Do you run the client as root? Do `ls -l` on the
tty (/dev/tty1 or /dev/ptysomething) for the permissions.
Does the syslog say anything interesting after you try the client?
With xinetd listening on talk port, do `strace -o file.st talk`.
> service talk
> {
> disable = no
> socket_type = dgram
> wait = yes
> user = nobody
> group = tty
> server = /usr/sbin/in.talkd
> }
If it doesn't work, try:
server = /usr/bin/strace -o /tmp/file.st /usr/sbin/in.talkd
I'm betting it is a permission error. See:
/tmp/.X11-unix:
total 0
srwxrwxrwx 1 root root 0 May 27 07:53 X0
That file, /tmp/.X11-unix/X0, is a Unix filesystem domain socket. It
behaves almost exactly the same way as an Internet IP address domain
socket on localhost: it is the name of an IP socket that never leaves
your machine, only instead of 127.0.0.1:25, say, its address is
/tmp/.X11-unix/X0.
Access to a Unix domain socket is governed by standard file permissions.
(So too with ttys.) I think your permissions are screwed up.
--
-114
If life is to exist in a Universe of this size, one thing it
can't afford to have is a sense of proportion. -- Douglas Adams