Next
Previous
Table of Contents
Answer: No, it won't. For that, ktalk must behave like
a ytalk, so that it is recognized as a ytalk by another client.
ytalk clients recognize each other by the character they use for
deleting. ytalk uses ASCII character 254. This often leads to
problems when talking to another talk client. (Who never saw the
problem of a backspace key not working?) To prevent these problems
ktalk uses the standart character 8 for deleting, so it isn't
recognized as a ytalk by another ytalk client. So ytalk
conferencing will not be possible.
Conferencing between ktalk clients is possible of course, and will
be implemented soon.
Answer: When a talk request is sent to your host, the inet daemon
starts the talk daemon "ktalkd". (For installing ktalkd, have a look at the
README file there.) ktalkd then starts ktalkdlg, if the person is logged
on and is working on an X terminal. ktalkdlg opens a window with a message
for the user, that a talk request arrived. ktalkdlg can now start ktalk, and
ktalk will establish the connection to the person who wanted to talk to you.
ktalk has to be inserted into the shared configuration file of ktalkd and
ktalkdlg so that it is started correctly. This configuration file can most
often be found at "/opt/kde/share/config/ktalkdrc" or
"/usr/local/kde/share/config.ktalkdrc". Within this file, change the entry
talkprg=...
to
talkprg=/opt/kde/bin/ktalk
(with the correct path name of the executable ktalk
file).
If you append the parameter "--autoexit
" to this line,
ktalk will quit automatically after closing the last connection.
New:
Since version 0.8.9 of ktalkd the daemon sends all incoming talk requests to
a running ktalk client. In this case, the ktalk client does the announcement
itself. ktalkdlg isn't started at all in that case.
Answer: In that case your system will probably have two different
IP addresses: One in the local network and the other one of your internet
provider. To be able to communicate with a talk daemon, ktalk must tell it
it's own IP address. But that's no easy task, if there is more than one. On
Linux it can be determinated with a "connect" on a datagram socket, on other
operating systems that trick doesn't work.
So problems will only arise on an operating system other than linux, and only
if your system is in more than one network.
Maybe in a future version of ktalk there will be the possibility to specify
the own IP address in dependance of the destination. So at least an expert
could solve the problem.
Answer: In the current version of ktalk this isn't possible indeed.
If you try to start ktalk a second time, the client already running will be
invoked instead. A future version of ktalk will contain the feature of more
than one main window with the same client. But because this corresponds with
the planned feature of conferencing, this feature wasn't integrated because
of lack of time.
Next
Previous
Table of Contents