ktalk-0.2.7-5.alpha.rpm/usr/share/doc/HTML/en/ktalk/ktalk-7.html

pkg://ktalk-0.2.7-5.alpha.rpm:250535/usr/share/doc/HTML/en/ktalk/ktalk-7.html info downloads
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
  <TITLE>The ktalk Handbook: Questions and answers</TITLE>
  <META HTTP-EQUIV="content-type" CONTENT="text/html; charset=iso-8859-1">
  <META NAME="keywords" CONTENT="KTALK talk talkd ntalk">
  <META NAME="description" CONTENT="KTALK talk talkd ntalk">
</HEAD>

<BODY BGCOLOR="#ffffff" LINK="#aa0000" TEXT="#000000" > 
<FONT FACE="Helvetica">
  <A HREF="http://www.kde.org/"><IMG SRC="logotp3.gif" BORDER="0" ALT="The K Desktop Environment"></A>
  <HR WIDTH="100%" SIZE=2 NOSHADE>
<P ALIGN="RIGHT">
  <A HREF="ktalk-8.html">Next</A>
  <A HREF="ktalk-6.html">Previous</A>
  <A HREF="index.html#toc7">Table of Contents</A>
<P>
  <H3><A NAME="s7">7. Questions and answers</A></H3>
<P>
  <H3><A NAME="ss7.1">7.1 Will ktalk be compatible with the conferencing of ytalk in the future?</A></H3>
  <UL>
  <EM>Answer:</EM> 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.
<P>
  Conferencing between ktalk clients is possible of course, and will 
  be implemented soon. 
  </UL>

  <H3><A NAME="ss7.2">7.2 How do ktalk, ktalkd and ktalkdlg work
      together?</A></H3>
  <UL>
  <EM>Answer:</EM> 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.
  <P>
  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
  <BLOCKQUOTE><CODE>talkprg=...</CODE></BLOCKQUOTE>
  to
  <BLOCKQUOTE><CODE>talkprg=/opt/kde/bin/ktalk</CODE></BLOCKQUOTE>
  (with the correct path name of the executable <CODE>ktalk</CODE> file).<P>
  If you append the parameter "<CODE>--autoexit</CODE>" to this line,
  ktalk will quit automatically after closing the last connection.<P>
  <B>New:</B><BR>
  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.
  </UL>

  <H3><A NAME="ss7.3">7.3 Why doesn't ktalk work sometime, if I have a
      network device and a modem?</A></H3>
  <UL>
  <EM>Answer:</EM> 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.<BR>
  So problems will only arise on an operating system other than linux, and only
  if your system is in more than one network.<BR>
  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.<P>
  </UL>

  <H3><A NAME="ss7.4">7.4 How do I open more than one ktalk window?</A></H3>
  <UL>
  <EM>Answer:</EM> 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.<P>
  </UL>

<P ALIGN="RIGHT">
  <A HREF="ktalk-8.html">Next</A>
  <A HREF="ktalk-6.html">Previous</A>
  <A HREF="index.html#toc7">Table of Contents</A>
<P ALIGN="CENTER">
  <HR WIDTH="100%" SIZE=3 NOSHADE>
</FONT>
 
</BODY>
</HTML>