Section: Maintenance Commands (8)Updated: 1995 April 11Local indexUp
gtalkd - GNU talk daemon
is a talk daemon which is fully compatible with
which is the
provides a talk service via the internet. A user may use a
to send a UDP message to
which will then provide the services of storing invitations, and making
announcements to a user's terminal.
Command line switches are:
Emulate the BSD post 4.2 talk protocol by not accepting any GNU talk
Open a socket and loop on it forever. Unlike running under inetd
during which stdin and stdout provides the socket necessary for
communication, this option lets the talk daemon run as a separate self
Run using the GNU talk protocol extensions. This is the default.
Print process help.
Simulate the pre BSD 4.2 talk protocol which is commonly found on
SunOS and Solaris.
This option is run as an extended option for the --sun option.
Instead of acting as a daemon and answering requests, all requests are
sent to the n/gtalk daemon on the same machine. Answers are received
and forwarded back the the requester.
Send all error and verbose messages to the controlling TTY. In
addition, create and bind the correct socket by hand instead of
inheriting it through stdin and stdout.
Print out verbose information, or verbose syslog information.
Print out the current version of gtalkd.
The GNU talk daemon can be placed in a system bin such as
and then installed in the
file in place of the normal talk daemon which may be found there. The
resulting configuration in
should contain the following lines:
In addition, if you are installing on SunOS or Solaris, you will have
to make it aware of the ntalk service. This service is found in
Simply find the line which says:
and add the line
right after it.
Contains definitions for the Internet Super Server to start gtalkd.
This file contains information relating names socket/service
information to names. It is used to determine the "[n]talk" socket
used when in forever mode.
Accessing /etc/passwd in the usual way allows
to determine a users home directory to read their personal ringer
file. The ringer file allows
to forward announcements directly to an interested process.
Different individuals may start applications which create and manage
this file. The file contains a UDP socket definition which allows
to automatically pass the announcement information directly to a
process which cares.
This is read by gtalkd to determine of a pattern matches an incomming call
for the callee. If it does, then the requested response is returned.
A pattern is of the form
The username is a string which must match the incomming caller's id exactly.
The hostname can be a substring of the caller's host name to match.
One of username or hostname can be blank, which conflicts defaulting first to
username only matches, and then to complete username,hostname combinations.
Valid DENY_METHODS are
, which allows a pattern to announce to you, and
, which cause
to predent you are not logged on.
sends a failure message, and
pretends that you have permissions turned off on your tty.
means to send a specific message back saying that you have chosen to
specifically prevent that person from calling you.
If their client is not GTALK compliant, then it is downgraded to
Different locations of utmp which contain login information for
different users. This file is referenced to determine which TTY
device to open in order to write an announcement message.
Terminal devices users are attached to. These devices are opened in
order to write an announcement message.