1.\" Copyright (c) 1983, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 3. Neither the name of the University nor the names of its contributors 13.\" may be used to endorse or promote products derived from this software 14.\" without specific prior written permission. 15.\" 16.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 19.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 26.\" SUCH DAMAGE. 27.\" 28.\" @(#)talkd.8 8.2 (Berkeley) 12/11/93 29.\" 30.Dd December 11, 1993 31.Dt TALKD 8 32.Os 33.Sh NAME 34.Nm talkd 35.Nd remote user communication server 36.Sh SYNOPSIS 37.Nm 38.Sh DESCRIPTION 39The 40.Nm 41utility 42is the server that notifies a user that someone else wants to 43initiate a conversation. 44It acts as a repository of invitations, responding to requests 45by clients wishing to rendezvous to hold a conversation. 46In normal operation, a client, the caller, 47initiates a rendezvous by sending a 48.Tn CTL_MSG 49to the server of 50type 51.Tn LOOK_UP 52(see 53.In protocols/talkd.h ) . 54This causes the server to search its invitation 55tables to check if an invitation currently exists for the caller 56(to speak to the callee specified in the message). 57.Pp 58If the lookup fails, 59the caller then sends an 60.Tn ANNOUNCE 61message causing the server to 62broadcast an announcement on the callee's login ports requesting contact. 63.Pp 64When the callee responds, the local server uses the 65recorded invitation to respond with the appropriate rendezvous 66address and the caller and callee client programs establish a 67stream connection through which the conversation takes place. 68.Sh SEE ALSO 69.Xr talk 1 , 70.Xr write 1 71.Sh HISTORY 72The 73.Nm 74utility appeared in 75.Bx 4.3 . 76