debian man page for xtelld

Query: xtelld

OS: debian

Section: 8

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

XTELLD(8)						      System Manager's Manual							 XTELLD(8)

NAME
xtelld - daemon receiving messages from xtell(1) clients
SYNOPSIS
xtelld [options]
DESCRIPTION
xtelld is daemon receiving messages from the xtell(1) client and displaying them to apropriate user.
OPTIONS
--help Short help --alone Force server to run standalone --inetd Force server to act as service of inetd --version Print version information and exit. -sX Lifetime for spawned services (in seconds) ex: -s25 maintain connections for up to 25 seconds -mX Spawn no more than X children services at a time ex: -m15 service no more than 15 requests at once. Note: ignored if inetd service -pX Use port X, default: 4224 -n Do not lookup addresses, use IP numbers instead
USAGE
Xtell daemon can run either from inetd(preferred) or from command line. If you decide to start it from inetd, add this line to /etc/ser- vices : xtell 4224/tcp # xtell server and this line to /etc/inetd.conf : xtell stream tcp nowait nobody.tty /usr/sbin/tcpd /usr/local/sbin/xtelld Notice that the entries are separated by tabs, not spaces. Restart inetd with killall -HUP inetd What to do if you are a normal user and want to run xtell daemon: You can't run it from inetd, obviously. Just start ./xtelld to use xtell on default port (4224). In this case, xtell can write messages only to you. If there is another user on that system willing to get messages, either s/he starts xtelld on another port (e.g. ./xtelld -p4225), or makes his/her tty writable by you (e.g. chmod a+rw /dev/tty* /dev/pts/*)
AUTHOR
Radovan Garabik (garabik@fmph.uniba.sk)
SEE ALSO
xtell(1), write(1), talk(1), talkd(8), tty(1) XTELLD(8)
Related Man Pages
go500(8c) - redhat
kpropd(8) - redhat
p910nd(8) - debian
portslave(8) - debian
inetd.conf(4) - osf1
Similar Topics in the Unix Linux Community
Tcp wrapper
User defined service
inetd process
too many inetd running
Is this case is normal when programming in socket?