icecast2_config_file.html 20.8 KB
Newer Older
j's avatar
j committed
1 2 3 4 5 6 7 8 9
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<title>Icecast v2.0 Documentation</title>
<link rel="stylesheet" type="text/css" href="style.css" />
</head>
<body>
<div class="boxtest">
10 11
<body bgcolor="#efefef" text="#323232" link="#0000ff" vlink="#800080" alink="#ff0000">
<h1>Icecast 2 Config File</h1>
j's avatar
j committed
12
<table width="100%"><tr><td bgcolor="#007B79" height="10" align="center"></td></tr></table>
13 14
<h3>Overview</h3>
<p>
vanguardist's avatar
vanguardist committed
15
This section will describe each section of the config file and is grouped into the following sections:
16 17 18 19 20 21 22 23 24 25 26
</p>
<li><a href="#limits">Limits</a>
<li><a href="#authentication">Authentication</a>
<li><a href="#yp">YP Directory Settings</a>
<li><a href="#misc">Misc Server settings</a>
<li><a href="#relay">Relay settings</a>
<li><a href="#mount">Mount Specific settings</a>
<li><a href="#path">File path settings</a>
<li><a href="#log">Logging</a>
<li><a href="#security">Security</a>

j's avatar
j committed
27 28 29
<br />
<br />
<br />
30 31 32 33
<a name="limits"></a>
<h2>Limits</h2>
<pre>
    &lt;limits&gt;
34 35 36 37 38 39 40 41 42 43
        &lt;clients&gt;100&lt;/clients&gt;
        &lt;sources&gt;2&lt;/sources&gt;
        &lt;threadpool&gt;5&lt;/threadpool&gt;
        &lt;queue-size&gt;102400&lt;/queue-size&gt;
        &lt;client-timeout&gt;30&lt;/client-timeout&gt;
        &lt;header-timeout&gt;15&lt;/header-timeout&gt;
        &lt;source-timeout&gt;10&lt;/source-timeout&gt;
        &lt;burst-on-connect&gt;1&lt;/burst-on-connect&gt;
        &lt;burst-size&gt;65536&lt;/burst-size&gt;
    &lt;/limits&gt;
44
</pre>
vanguardist's avatar
vanguardist committed
45
<p>This section contains server level settings that, in general, do not need to be changed.  Only modify this section if you are know what you are doing.
46 47
</p>
<h4>clients</h4>
j's avatar
j committed
48
<div class="indentedbox">
vanguardist's avatar
vanguardist committed
49
Total number of concurrent clients supported by the server.  Listeners are considered clients, but so is accesses to any static content (i.e. fileserved content) and also any requests to gather stats.  These are max *concurrent* connections for the entire server (not per mountpoint).
50 51
</div>
<h4>sources</h4>
j's avatar
j committed
52
<div class="indentedbox">
vanguardist's avatar
vanguardist committed
53
Maximum number of connected sources supported by the server.
54 55
</div>
<h4>threadpool</h4>
j's avatar
j committed
56
<div class="indentedbox">
57 58 59
This is the number of threads that are started to handle client connections.  You may need to increase this value if you are running a high traffic stream.  This recommended value is for a small to medium traffic server.
</div>
<h4>queue-size</h4>
j's avatar
j committed
60
<div class="indentedbox">
61 62 63
This is the maximum size (in bytes) of a client (listener) queue.  A listener may temporarily lag behind due to network congestion and in this case an internal queue is maintained for each listener.  If the queue grows larger than this config value, then the listener will be removed from the stream.
</div>
<h4>client-timeout</h4>
j's avatar
j committed
64
<div class="indentedbox">
65 66 67
This does not seem to be used.
</div>
<h4>header-timeout</h4>
j's avatar
j committed
68
<div class="indentedbox">
vanguardist's avatar
vanguardist committed
69
The maximum time (in seconds) to wait for a request to come in once the client has made a connection to the server.  In general this value should not need to be tweaked.
70 71
</div>
<h4>source-timeout</h4>
j's avatar
j committed
72
<div class="indentedbox">
73 74
If a connected source does not send any data within this timeout period (in seconds), then the source connection will be removed from the server.
</div>
75
<h4>burst-on-connect</h4>
j's avatar
j committed
76
<div class="indentedbox">
77 78
With this enabled, a connecting client will be sent a burst of audio data from the stream.  This will have the effect of reducing the startup time for the stream from the perspective of the listener.  This is due to the fact that most media players have local buffers that must be filled before the stream begins to play.  This may introduce a small latency in the stream (difference in time between when the source plays a clip and the listener hears a clip).  If this latency is important to you, then you can disable this feature.  The latency is bitrate-dependent, but as an example, for a 128kbps stream, the latency between the source and the player is ~ 1.5 secs WITHOUT burst on connect, and WITH burst on connect the latency is 3 secs.
</div>
79
<h4>burst-size</h4>
j's avatar
j committed
80
<div class="indentedbox">
81 82 83 84 85
The burst size is the amount of data (in bytes) to burst to a client at connection time. Like
burst-on-connect, this is to quickly fill the pre-buffer used by media players. The default
is 64kbytes which is a typical size used by most clients so changing it is not usually required.
This setting applies to all mountpoints.
</div>
j's avatar
j committed
86 87 88
<br />
<br />
<br />
89 90 91 92
<a name="authentication"></a>
<h2>Authentication</h2>
<pre>
    &lt;authentication&gt;
93 94 95 96 97
        &lt;source-password&gt;hackme&lt;/source-password&gt;
        &lt;relay-password&gt;hackme&lt;/relay-password&gt;
        &lt;admin-user&gt;admin&lt;/admin-user&gt;
        &lt;admin-password&gt;hackme&lt;/admin-password&gt;
    &lt;/authentication&gt;
98 99 100 101
</pre>
<p>This section contains all the users and passwords used for administration purposes or to connect sources and relays.
</p>
<h4>source-password</h4>
j's avatar
j committed
102
<div class="indentedbox">
103 104 105
The unencrypted password used by sources to connect to icecast2.  Currently, the username for all source connections must be 'source'.  This is likely to change in the future.
</div>
<h4>relay-password</h4>
j's avatar
j committed
106
<div class="indentedbox">
107 108 109 110
Currently not used.
</div>
<h4>admin-user</h4>
<h4>admin-password</h4>
j's avatar
j committed
111
<div class="indentedbox">
112 113
The username/password used for all administration functions.  This includes retrieving statistics, accessing the web-based administration screens, etc.  A list of these functions can be found in the "Administration" section of the manual.
</div>
j's avatar
j committed
114 115 116
<br />
<br />
<br />
117 118 119 120
<a name="yp"></a>
<h2>YP Directory Settings</h2>
<pre>
    &lt;directory&gt;
121 122 123
        &lt;yp-url-timeout&gt;15&lt;/yp-url-timeout&gt;
        &lt;yp-url&gt;http://dir.xiph.org/cgi-bin/yp-cgi&lt;/yp-url&gt;
    &lt;/directory&gt;
124 125 126 127
</pre>
<p>This section contains all the settings for listing a stream on any of the Icecast2 YP Directory servers.  Multiple occurances of this section can be specified in order to be listed on multiple directory servers.
</p>
<h4>yp-url-timeout</h4>
j's avatar
j committed
128
<div class="indentedbox">
129 130 131
This value is the maximum time icecast2 will wait for a response from a particular directory server.  The recommended value should be sufficient for most directory servers.
</div>
<h4>yp-url</h4>
j's avatar
j committed
132
<div class="indentedbox">
133 134
The URL which icecast2 uses to communicate with the Directory server.  The value for this setting is provided by the owner of the Directory server.
</div>
j's avatar
j committed
135 136 137
<br />
<br />
<br />
138 139 140 141 142 143
<a name="misc"></a>
<h2>Misc Server Settings</h2>
<pre>
    &lt;hostname&gt;localhost&lt;hostname&gt;

    &lt;-- You can use these two if you only want a single listener --&gt;
144 145
    &lt;-- &lt;port&gt;8000&lt;/port&gt; --&gt;
    &lt;-- &lt;bind-address&gt;127.0.0.1&lt;/bind-address&gt; --&gt;
146

147
    &lt;-- You may have multiple &lt;listen-socket&gt; elements --&gt;
148
    &lt;listen-socket&gt;
149 150 151
        &lt;port&gt;8000&lt;/port&gt;
        &lt;bind-address&gt;127.0.0.1&lt;/bind-address&gt;
    &lt;/listen-socket&gt;
152

153
    &lt;fileserve&gt;1&lt;/fileserve&gt;
154 155 156 157
</pre>
<p>This section contains miscellaneous server settings.  Note that multiple listen-socket sections may be configured in order to have icecast2 listen on multiple network interfaces.  If a bind-address is not specified for a particular listen-socket, then the hostname parameter will be used to specify the address that will be bound.
</p>
<h4>port</h4>
j's avatar
j committed
158
<div class="indentedbox">
159 160 161
The TCP port that will be used to accept client connections.
</div>
<h4>bind-address</h4>
j's avatar
j committed
162
<div class="indentedbox">
163 164 165
And option IP address that can be used to bind to a specific network card.  If not supplied, then &lt;hostname&gt; will be used.
</div>
<h4>fileserve</h4>
j's avatar
j committed
166
<div class="indentedbox">
167 168
This flag turns on the icecast2 fileserver from which static files can be served.  All files are served relative to the path specified in the &lt;paths&gt;&lt;webroot&gt; configuration setting.
</div>
j's avatar
j committed
169 170 171
<br />
<br />
<br />
172 173 174
<a name="relay"></a>
<h2>Relay Settings</h2>
<pre>
175 176 177 178
    &lt;master-server&gt;127.0.0.1&lt;/master-server&gt;
    &lt;master-server-port&gt;8001&lt;/master-server-port&gt;
    &lt;master-update-interval&gt;120&lt;/master-update-interval&gt;
    &lt;master-password&gt;hackme&lt;/master-password&gt;
179 180

    &lt;relay&gt;
181 182 183 184 185 186
        &lt;server&gt;127.0.0.1&lt;/server&gt;
        &lt;port&gt;8001&lt;/port&gt;
        &lt;mount&gt;example.ogg&lt;/mount&gt;
        &lt;local-mount&gt;different.ogg&lt;/local-mount&gt;
        &lt;relay-shoutcast-metadata&gt;0&lt;/relay-shoutcast-metadata&gt;
    &lt;/relay&gt;
187
</pre>
vanguardist's avatar
vanguardist committed
188
<p>This section contains the server's relay settings. There are two types of relays: a "Master server relay" or a "Specific Mountpoint relay."  A Master server relay is only supported between icecast2 servers and is used to relays all mountpoints on a remote icecast2 server.   
189 190

<h3>Master Relay</h3>
vanguardist's avatar
vanguardist committed
191
The following diagram shows the basics of doing a Master relay.  Note that Server 1 is configured with the &lt;master-server&gt;, &lt;master-server-port&gt;, etc settings and Server 2 is the server from which Server 1 will pull all attached mountpoints and relay them.  Using a Master Server relay, ALL mountpoints on Server 2 will be relayed.  If only specific mountpoints need to be relayed, then you must configure Server 1 as a "Specific Mountpoint Relay".  Both Master server relays and Specific Mountpoint relays begin their "relaying" when the Server is started.
192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211

<pre>
      |-----|                       |-----|
      |     |  all mountpoints      |     | /mount1
      |     | &lt;-------------------  |     | /mount2.ogg
      |-----|                       |-----| /mount3
      Icecast 2                     Icecast 2 
      Server 1                      Server 2
      (RELAY SERVER)                (MASTER SERVER)

     configured with
     &lt;master-server&gt;
     settings 

</pre>

A server is configured as a Master Server relay by specifying the &lt;master-server&gt;, &lt;master-server-port&gt;,&lt;master-update-interval&gt;,&lt;master-password&gt; values in the config file.  The server that is being relayed does not need any special configuration.

</p>
<h4>master-server</h4>
j's avatar
j committed
212
<div class="indentedbox">
213 214 215
This is the IP for the server which contains the mountpoints to be relayed (Master Server).  
</div>
<h4>master-server-port</h4>
j's avatar
j committed
216
<div class="indentedbox">
217 218 219
This is the TCP Port for the server which contains the mountpoints to be relayed (Master Server).
</div>
<h4>master-update-interval</h4>
j's avatar
j committed
220
<div class="indentedbox">
vanguardist's avatar
vanguardist committed
221
The interval (in seconds) that the Relay Server will poll the Master Server for any new mountpoints to relay.
222 223
</div>
<h4>master-password</h4>
j's avatar
j committed
224
<div class="indentedbox">
225 226
This is the admin password on the Master server.  It is used to query the server for a list of mountpoints to relay.
</div>
j's avatar
j committed
227
<br />
228
<h3>Specific Mountpoint Relay</h3>
vanguardist's avatar
vanguardist committed
229
The following diagram shows the basics of doing a Specific Mountpoint relay.  Note that Server 1 is configured with the &lt;relay&gt; settings and Server 2 is the server from which Server 1 will pull the specified mountpoint(s) and relay them.  Using a Specific Mountpoint Relay, only those mountpoints specified on Server 1 will be relayed from Server 2.
230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248

<pre>
      |-----|                       |-----|
      |     |      /mount3          |     | /mount1
      |     | &lt;-------------------  |     | /mount2.ogg
      |-----|                       |-----| /mount3
      Icecast 2                     Icecast 2/Shoutcast/Icecast
      Server 1                      Server 2
      (RELAY SERVER)                (REMOTE SERVER)

     configured with
     &lt;relay&gt;
     settings 

</pre>

Specific Mountpoint Relays can be configured to relay from an Icecast 2 server, as well as Icecast 1.x and Shoutcast.
A server is configured as a Specific Mountpoint Server relay by specifying a &lt;relay&gt; XML chunk in the config file for each mountpoint to be relayed.  The server that is being relayed does not need any special configuration.

249 250 251 252 253 254 255 256 257
<pre>
    &lt;relay&gt;
        &lt;server&gt;127.0.0.1&lt;/server&gt;
        &lt;port&gt;8001&lt;/port&gt;
        &lt;mount&gt;example.ogg&lt;/mount&gt;
        &lt;local-mount&gt;different.ogg&lt;/local-mount&gt;
        &lt;relay-shoutcast-metadata&gt;0&lt;/relay-shoutcast-metadata&gt;
    &lt;/relay&gt;
</pre>
258 259 260

</p>
<h4>server</h4>
j's avatar
j committed
261
<div class="indentedbox">
262 263 264
This is the IP for the server which contains the mountpoint to be relayed.
</div>
<h4>port</h4>
j's avatar
j committed
265
<div class="indentedbox">
266 267 268
This is the TCP Port for the server which contains the mountpoint to be relayed.
</div>
<h4>mount</h4>
j's avatar
j committed
269
<div class="indentedbox">
vanguardist's avatar
vanguardist committed
270
The mountpoint located on the remote server.  If you are relaying a shoutcast stream, this must be '/'.
271 272
</div>
<h4>local-mount</h4>
j's avatar
j committed
273
<div class="indentedbox">
274 275 276
The name to use for the local mountpoint.  This is what the mount will be named on the RELAY SERVER.
</div>
<h4>relay-shoutcast-metadata</h4>
j's avatar
j committed
277
<div class="indentedbox">
vanguardist's avatar
vanguardist committed
278
If you are relaying a Shoutcast stream, you need to specify this indicator to also relay the metadata (song titles) that is part of the Shoutcast stream (1=enabled, 0=disabled).
279
</div>
j's avatar
j committed
280 281 282
<br />
<br />
<br />
283 284 285 286
<a name="mount"></a>
<h2>Mount Specific Settings</h2>
<pre>
    &lt;mount&gt;
287 288 289 290 291 292 293 294
        &lt;mount-name&gt;/example-complex.ogg&lt;/mount-name&gt;
        &lt;username&gt;othersource&lt;/username&gt;
        &lt;password&gt;hackmemore&lt;/password&gt;
        &lt;max-listeners&gt;1&lt;/max-listeners&gt;
        &lt;dump-file&gt;/tmp/dump-example1.ogg&lt;/dump-file&gt;
        &lt;fallback-mount&gt;example2.ogg&lt;/fallback-mount&gt;
        &lt;fallback-override&gt;1&lt;/fallback-override&gt;
        &lt;burst-size&gt;65536&lt;/burst-size&gt;
295 296
        &lt;authentication type="htpasswd"&gt;
                &lt;option name="filename" value="myauth"/&gt;
297
                &lt;option name="allow_duplicate_users" value="0"/&gt;
298 299
        &lt;/authentication&gt;

300
    &lt;/mount&gt;
301
</pre>
vanguardist's avatar
vanguardist committed
302
<p>This section contains settings which apply only to a specific mountpoint.  Within this section you can reserve a specific mountpoint and set a source username/password for that mountpoint (not yet implemented) as well as specify individual settings which will apply only to the supplied mountpoint.
303 304
</p>
<h4>mount-name</h4>
j's avatar
j committed
305
<div class="indentedbox">
306 307 308
The name of the mount point for which these settings apply.
</div>
<h4>username</h4>
j's avatar
j committed
309
<div class="indentedbox">
310 311 312
An optional value which will set the username that a source must use to connect using this mountpoint.
</div>
<h4>password</h4>
j's avatar
j committed
313
<div class="indentedbox">
314 315 316
An optional value which will set the password that a source must use to connect using this mountpoint.
</div>
<h4>max-listeners</h4>
j's avatar
j committed
317
<div class="indentedbox">
318 319 320
An optional value which will set the maximum number of listeners that can be attached to this mountpoint.
</div>
<h4>dump-file</h4>
j's avatar
j committed
321
<div class="indentedbox">
322 323 324
An optional value which will set the filename which will be a dump of the stream coming through on this mountpoint.
</div>
<h4>fallback-mount</h4>
j's avatar
j committed
325
<div class="indentedbox">
vanguardist's avatar
vanguardist committed
326
This specifies a mountpoint that is used in the case of a source disconnect.  If listeners are connected to the mount specified by the &lt;mount-name&gt; config value, then if the source is disconnected; all currently connected clients will be moved to the fallback-mount.
327
</div>
328
<h4>fallback-override</h4>
j's avatar
j committed
329
<div class="indentedbox">
330 331 332 333
When enabled, this allows a connecting source client or relay on this mountpoint to move
listening clients back from the fallback mount.
</div>
<h4>burst-size</h4>
j's avatar
j committed
334
<div class="indentedbox">
335 336 337
This optional setting allows for providing a burst size which overrides the default burst size
as defined in limits.  The value is in bytes.
</div>
338
<h4>authentication</h4>
j's avatar
j committed
339
<div class="indentedbox">
340
This specifies that the named mount point will require listener authentication.  Currently, we only support a file-based authentication scheme (type=htpasswd).  Users and encrypted password are placed in this file (separated by a :) and all requests for this mountpoint will require that a user and password be supplied for authentication purposes.  These values are passed in via normal HTTP Basic Authentication means (i.e. http://user:password@stream:port/mountpoint.ogg).  Users and Passwords are maintained via the web admin interface.  A mountpoint configured with an authenticator will display a red key next to the mount point name on the admin screens.  You can read more about listener authentication <a href="icecast2_listenerauth.html">here</a>.
341
</div>
j's avatar
j committed
342 343 344
<br />
<br />
<br />
345 346 347 348
<a name="path"></a>
<h2>Path Settings</h2>
<pre>
    &lt;paths&gt;
349 350 351 352 353
        &lt;basedir&gt;./&lt;/basedir&gt;
        &lt;logdir&gt;./logs&lt;/logdir&gt;
        &lt;pidfile&gt;./icecast.pid&lt;/pidfile&gt;
        &lt;webroot&gt;./web&lt;/webroot&gt;
        &lt;adminroot&gt;./admin&lt;/adminroot&gt;
354
        &lt;alias source="/foo" dest="/bar"/&gt;
355
    &lt;/paths&gt;
356 357 358 359
</pre>
<p>This section contains paths which are used for various things within icecast.  All paths should not end in a '/'.
</p>
<h4>basedir</h4>
j's avatar
j committed
360
<div class="indentedbox">
361 362 363
This path is used in conjunction with the chroot settings, and specified the base directory that is chrooted to when the server is started.  This feature is not supported on win32.
</div>
<h4>logdir</h4>
j's avatar
j committed
364
<div class="indentedbox">
365 366
This path specifies the base directory used for logging. Both the error.log and access.log will be created relative to this directory.  
</div>
367
<h4>pidfile</h4>
j's avatar
j committed
368
<div class="indentedbox">
369 370
This pathname specifies the file to write at startup and to remove at normal shutdown. The file contains the process id of the icecast process. This could be read and used for sending signals icecast.
</div>
371
<h4>webroot</h4>
j's avatar
j committed
372
<div class="indentedbox">
373 374 375
This path specifies the base directory used for all static file requests.  This directory can contain all standard file types (including mp3s and ogg vorbis files).  For example, if webroot is set to /var/share/icecast2, and a request for http://server:port/mp3/stuff.mp3 comes in, then the file /var/share/icecast2/mp3/stuff.mp3 will be served.
</div>
<h4>adminroot</h4>
j's avatar
j committed
376
<div class="indentedbox">
377 378 379
This path specifies the base directory used for all admin requests.  More specifically, this is used to hold the XSLT scripts used for the web-based admin interface.  The admin directory contained within the icecast distribution contains these files.
</div>
<h4>alias source="/foo" dest="/bar"</h4>
j's avatar
j committed
380
<div class="indentedbox">
381 382
Aliases are used to provide a way to create multiple mountpoints that refer to the same mountpoint.
</div>
j's avatar
j committed
383 384 385
<br />
<br />
<br />
386 387 388 389 390 391 392 393 394 395 396 397 398
<a name="log"></a>
<h2>Logging Settings</h2>
<pre>
    &lt;logging&gt;
        &lt;accesslog&gt;access.log&lt;/accesslog&gt;
        &lt;errorlog&gt;error.log&lt;/errorlog&gt;
      	&lt;loglevel&gt;4&lt;/loglevel&gt; &lt;-- 4 Debug, 3 Info, 2 Warn, 1 Error --&gt;
    &lt;/logging&gt;
</pre>
<p>This section contains information relating to logging within icecast.  There are two logfiles currently generated by icecast, an error.log (where all log messages are placed) and an access.log (where all stream/admin/http requests are logged).
</p>
<p>Note that on non-win32 platforms, a HUP signal can be sent to icecast in which the log files are re-opened for appending giving the ability move/remove the log files.
<h4>accesslog</h4>
j's avatar
j committed
399
<div class="indentedbox">
400 401 402
Into this file, all requests made to the icecast2 will be logged.  This file is relative to the path specified by the &lt;logdir&gt; config value.
</div>
<h4>errorlog</h4>
j's avatar
j committed
403
<div class="indentedbox">
404 405 406
All icecast generated log messages will be written to this file.  If the loglevel is set too high (Debug for instance) then this file can grow fairly large over time.  Currently, there is no log-rotation implemented.
</div>
<h4>loglevel</h4>
j's avatar
j committed
407 408
<div class="indentedbox">
Indicates what messages are logged by icecast.  Log messages are categorized into one of 4 types, Debug, Info, Warn, and Error.<br /><br />The following mapping can be used to set the appropraite value :
409
</div>
j's avatar
j committed
410 411
<br />
<br />
412 413 414 415
<li>loglevel = 4 - Debug, Info, Warn, Error messages are printed
<li>loglevel = 3 - Info, Warn, Error messages are printed
<li>loglevel = 2 - Warn, Error messages are printed
<li>loglevel = 1 - Error messages only are printed
j's avatar
j committed
416
<br />
417 418 419 420 421 422 423 424 425 426 427 428 429 430
<a name="security"></a>
<h2>Security Settings</h2>
<pre>
    &lt;security&gt;
        &lt;chroot&gt;0&lt;/chroot&gt;
        &lt;changeowner&gt;
            &lt;user&gt;nobody&lt;/user&gt;
            &lt;group&gt;nogroup&lt;/group&gt;
	&lt;/changeowner&gt;
    &lt;/security&gt;
</pre>
<p>This section contains configuration settings that can be used to secure the icecast server by performing a chroot to a secured location.  This is currently not supported on win32.
</p>
<h4>chroot</h4>
j's avatar
j committed
431
<div class="indentedbox">
432 433 434
An indicator which specifies whether a chroot() will be done when the server is started.  The chrooted path is specified by the &lt;basedir&gt; configuration value.
</div>
<h4>changeowner</h4>
j's avatar
j committed
435
<div class="indentedbox">
436 437 438 439 440
This section indicates the user and group that will own the icecast process when it is started.  These need to be valid users on the system.
</div>
</div>
</body>
</html>