

AUVOXWARE(1)					     AUVOXWARE(1)


NNAAMMEE
       auvoxware  -  Network Audio System server for PCs with the
       VOXware audio interface

SSYYNNOOPPSSIISS
       aauuvvooxxwwaarree [:listen port offset] [-option ...]

DDEESSCCRRIIPPTTIIOONN
       _a_u_v_o_x_w_a_r_e is the NAS server used on PC Unix platforms that
       support	the  VOXware  device  drivers  for  popular sound
       cards. It is able to discover what each device has in  the
       way  of	ability	 and  configure itself appropriately. The
       known list of platforms that support the VOXware interface
       are  Linux,  FreeBSD, SCO, Unixware and the generic SVR4.2
       unixes.

SSTTAARRTTIINNGG TTHHEE SSEERRVVEERR
       The server is usually started from  /etc/rc  or	a  user's
       startup script.

       When  the  Network Audio System server starts up, it takes
       over /dev/dsp & /dev/dsp1, according to	the  instructions
       in its configuration file, if any.  Note that applications
       that attempt to access these devices themselves will  fail
       while  it  is  running.	 It will look for a configuration
       file of the name nasd.conf in the config	 directory,  e.g.
       /etc/nas/nasd.conf.  If it finds one, it will then open it
       and parse the contents, setting up the inputs and  outputs
       as required.

OOPPTTIIOONNSS
       All of the Network Audio System servers accept the follow-
       ing command line options:

       --aaaa     Allows  clients	on  any	 host  to  connect.    By
	       default,	 access is allowed only to clients on the
	       local host.

SSIIGGNNAALLSS
       The Network Audio System server attaches	 special  meaning
       to the following signals:

       _S_I_G_H_U_P  This  signal causes the server to close all exist-
	       ing connections, free all resources,  and  restore
	       all defaults.

       _S_I_G_T_E_R_M This signal causes the server to exit cleanly.

       _S_I_G_U_S_R_1 This  signal is used quite differently from either
	       of the above.  When the server starts,  it  checks
	       to  see	if  it	has  inherited SIGUSR1 as SIG_IGN
	       instead of the usual SIG_DFL.  In this  case,  the
	       server sends a SIGUSR1 to its parent process after
	       it has set up the various connection schemes.


								1


AUVOXWARE(1)					     AUVOXWARE(1)


DDIIAAGGNNOOSSTTIICCSS
       Too numerous to list  them  all.	  If  run  from	 _i_n_i_t_(_8_),
       errors	  are	 typically    logged	in    the    file
       _/_u_s_r_/_a_d_m_/_a_u_d_i_o_*_m_s_g_s,

FFIILLEESS
       /tmp/.sockets/audio*	     Unix domain socket

       /usr/adm/audio*msgs

       /dev/audio		     Audio device

SSEEEE AALLSSOO
       nas(1), auinfo(1), auplay(1), auctl(1), nasd.conf(1)

BBUUGGSS
       If _a_u dies before its clients, new clients won't	 be  able
       to  connect  until all existing connections have their TCP
       TIME_WAIT timers expire.

       The current access control support is weak at best.


CCOOPPYYRRIIGGHHTT
       Copyright 1993, Network Computing Devices, Inc.

AAUUTTHHOORRSS
       The auvoxware server contains much code from the sun  sam-
       ple  server,  written  originally  by  Greg Renda and Dave
       Lemke of NCD, who in turn borrowed much code from the sam-
       ple  X  server.	The original VOXware server for Linux was
       written by Amancio Hasty (hasty@rah.star-gate.com) and was
       merged  with  the  SVR4 VOXware server, written by Stephen
       Hocking	    (sysseh@devetir.qld.gov.au).	Christian
       Schlichtherle  (s_schli@ira.uka.de)  then  added some more
       Linux fixes, code to allow full duplex operation on  those
       cards  that  supported  it (GUS, PAS16, AudioTriX) and did
       some work on the 16 bit code. Stephen Hocking made sure it
       ran  under  FreeBSD. Shawn M. (shawnm@sco.com) fixed it up
       to run under SCO Unix and added code to dynamically adjust
       the buffer sizes.  Stephen Hocking then added code for the
       server to use a configuration file.

       The sample X server was originally written by Susan  Ange-
       branndt,	 Raymond Drewry, Philip Karlton, and Todd Newman,
       from Digital Equipment Corporation, with	 support  from	a
       large  cast.   It  has since been extensively rewritten by
       Keith Packard and Bob Scheifler, from MIT.


								2