roar_socket_listen(3) [debian man page]
roar_socket_listen(3) System Manager's Manual: RoarAudio roar_socket_listen(3) NAME
roar_socket_listen - Opens a new listen socket SYNOPSIS
#include <roaraudio.h> int roar_socket_listen(int type, char * host, int port); DESCRIPTION
Opens a new listening socket for network clients to connect to. You may accept new connections via accept(2). PARAMETERS
type The type of the Socket. See the list below. host The host or path name to listen on. This depends on the type argument. For TCP/IP to listen on any interface use a value of "0.0.0.0". port The port number to listen on. This may be ignored by types not supporting port numbers. SOCKET TYPES
ROAR_SOCKET_TYPE_UNKNOWN The type will be auto detected. Don't use this if you know the type. Only use this to support user given addresses and enable auto detection. ROAR_SOCKET_TYPE_TCP Use a TCP/IP connection. This is standard mode for networking. host is the hostname or IP to listen on and port is the port number to use. ROAR_SOCKET_TYPE_INET Same as above but deprecated. Use ROAR_SOCKET_TYPE_TCP. ROAR_SOCKET_TYPE_UNIX UNIX Domain Socket. This should be default for local connections. host is the filename of the socket. ROAR_SOCKET_TYPE_DECNET DECnet socket. ROAR_SOCKET_TYPE_FORK This is to fork a roard to communicate with. Can't be use to listen on, just to connect to. host and port is ignored at the moment. ROAR_SOCKET_TYPE_FILE This is used to open a plain file. Can't be use to listen on, just to connect to. host is the filename to connect to. RETURN VALUE
On success these calls return filehandle. On error, -1 is returned. BUGS
Listening on UDP sockets is not supported at the moment. EXAMPLES
FIXME SEE ALSO
accept(2), libroar(7), RoarAudio(7). RoarAudio May 2011 roar_socket_listen(3)
Check Out this Related Man Page
roartips(7) System Manager's Manual: RoarAuido roartips(7) NAME
roartips - Tips for RoarAudio users SYNOPSIS
roard [OPTIONS...] ... roarclient [OPTIONS...] ... DESCRIPTION
This manpage lists some tips for intermedia to advanced users of RoarAudio. CONTROLLING ROARD
RoarAudio supports a lot of things you can change on the fly. This includes the volume for each stream as you may allready noticed: If you cange the volume within a player only this stream is changed, other streams keep there loudness. There a a lot other things that can be changed on the fly. To do this there is a tool called roarctl(1). You may want to play around a bit with it. A good start are to try those two commands: roarctl --help roarctl allinfo The later one will show you all information current available of the server it self, the clients and the streams. This may include a lot of information. SERVER ADDRESS
There a serverel types of server addresses based on the protocol used to communicate. This lists the corrently implemented types in order of importance: /path/to/sock Path to UNIX Domain Socket. Example: /tmp/roar host, host:port This is used for connections over TCP/IP. If port is omitted the default port is used. Examples: audio.homeserver.local localhost:7564 node::, node::object, ::object, :: This is the way to specify a DECnet connection to node node's object object. Both may be omitted to use defaults. Default node name is local hosts node name. Examples: mynode:: ::roar yournode::yourroard +fork This starts a new roard for every roar_connect(3). This is used internaly by the lib to emulate EsounD's fallback. ENVIRONMENT
ROAR_SERVER This varibale contains the default server address. If some client does not allow a user to set a server address or to set a default value this one come into play. Examples: ROAR_SERVER=some.host ROAR_SERVER=another.host:port ROAR_SERVER=node:: ROAR_SERVER=/tmp/roar SEE ALSO
roarcat(1), roarctl(1), roarfilt(1), roarfish(1), roarmon(1), roarvorbis(1), roard(1), libroar(7). RoarAudio August 2008 roartips(7)