fox2mike 05/06/28 19:17:44 Modified: xml/htdocs/doc/en shoutcast-config.xml Log: Fixed a gazillion typos, a bit of grammar, CC-BY-SA to 2.5 etc. **No Content Changes**. No thanks to chriswhite coz he asked for the typo-check ;)
Revision Changes Path 1.8 +46 -41 xml/htdocs/doc/en/shoutcast-config.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/shoutcast-config.xml?rev=1.8&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/shoutcast-config.xml?rev=1.8&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/shoutcast-config.xml.diff?r1=1.7&r2=1.8&cvsroot=gentoo Index: shoutcast-config.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/shoutcast-config.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- shoutcast-config.xml 16 Apr 2005 20:01:02 -0000 1.7 +++ shoutcast-config.xml 28 Jun 2005 19:17:44 -0000 1.8 @@ -1,23 +1,27 @@ <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/shoutcast-config.xml,v 1.7 2005/04/16 20:01:02 swift Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/shoutcast-config.xml,v 1.8 2005/06/28 19:17:44 fox2mike Exp $ --> <guide link="shoutcast-config.xml"> <title>Streaming Radio With SHOUTcast</title> -<author title="Main Author"> +<author title="Author"> <mail link="[EMAIL PROTECTED]">Chris White</mail> </author> +<author title="Editor"> + <mail link="[EMAIL PROTECTED]">Shyam Mani</mail> +</author> <abstract> -This guide will walk through the steps needed to setup a streaming radio server with SHOUTcast Server and SHOUTcast Trans. +This guide will walk through the steps needed to setup a streaming radio server +with SHOUTcast Server and SHOUTcast Trans. </abstract> <!-- The content of this document is licensed under the CC-BY-SA license --> -<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> +<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> <version>1.3</version> -<date>2005-04-16</date> +<date>2005-06-29</date> <chapter> <title>Setting up SHOUTcast Server</title> @@ -84,9 +88,9 @@ it is foolish to setup 100 users on a 256kbs upload (This is what I have set, as my upload is about that). If you're running SHOUTcast Server to serve a LAN, you can probably set this MUCH higher (to the 100 mentioned easily). -Please remember to not abuse whatever bandwith you are using though. Bandwith -is a high cost to ISP's and service providers, and some will cut your account, -fine you high costs to makeup, or both. +Please remember to not abuse whatever bandwith you are using though. Bandwidth +comes at quite a high price to ISP's and some will cut your account, fine you +high costs to makeup, or both. </p> <pre caption="Setting the password"> @@ -114,7 +118,7 @@ ; the DNAS is setting up a socket on startup, make sure nothing else on the ; machine is running on the same port (telnet localhost portnumber -- if you ; get connection refused then you're clear to use that port). Ports less than 1024 -; may require root privledges on *nix machines. The default port is 8000.</comment> +; may require root privileges on *nix machines. The default port is 8000.</comment> PortBase=8000 </pre> @@ -165,7 +169,7 @@ </pre> <p> -This is disabled by default in the ebuild to, once again, run the daemon as +This is disabled by default in the ebuild to make the daemon run as silently as possible. This will log any events (connects, disconnects, etc) to stdout as they happen in realtime. However, because the log file does the same thing, I recommend using it instead. @@ -179,7 +183,7 @@ <p> Just as it states, this value will set how many of the most recently played -/played.html will display. If you put more than 20, you should probably +/played.html will display. If you put more than 20, you should probably consider more coffee. </p> @@ -212,7 +216,7 @@ <p> This specifies whether or not you want to log hits to the http server that -SHOUTcast provides. Once again, recommended for those who wish the most +SHOUTcast provides. Once again, recommended for those who wish the most secure logging possible, but not recommended for home/casual users. </p> @@ -230,8 +234,8 @@ </pre> <p> -The first option enables W3C logging. This type of logging is easily parsable -by the recommended programs listed. Highly recommended for those who wish to +The first option enables W3C logging. This type of logging can be easily parsed +by the programs listed. This is highly recommended for those who wish to have the most in depth statistics possible. The second option specifies where to store the W3C log. This is set to /dev/null by the ebuild. </p> @@ -301,9 +305,9 @@ </pre> <p> -This options specifies whether or not you want to preform reverse DNS lookups -on clients. This would take their host and give you an IP. Use this for -logging purposes to create a more detailed report. +This option specifies whether or not you want to perform reverse DNS lookups +on clients. This would take an IP address and try to find out the corresponding +hostname. Use this for logging purposes to create a more detailed report. </p> <pre caption="Setting up relaying"> @@ -316,11 +320,11 @@ </pre> <p> -This specifies that you are acting as a relay server. Relay servers are +This specifies that you are acting as a relay server. Relay servers are often used to take a low bandwith connection that can only stream to one client, and use its own higher bandwith to serve to more clients. RelayPort specifies the port and IP address of the SHOUTcast Server you wish to -relay for. Comment this out if you don't plan on using your server as a relay. +relay for. Comment this out if you don't plan on using your server as a relay. </p> </body> @@ -342,10 +346,10 @@ </pre> <p> -Setting this will create a broadcaster and administrator. The broadcaster can -log in with Password, and view connections. However, should the person want -to kick/ban/administer the server, they must have the Admin password. This -option creates more pecific roles for your server. This is recommended for +Setting this will create a broadcaster and administrator. The broadcaster can +log in with Password, and view connections. However, should the person want +to kick/ban/administer the server, they must have the Admin password. This +option creates more specific roles for your server. This is recommended for instances where the system administrator is not the same person as the broadcaster. </p> @@ -372,27 +376,27 @@ <p> This specifies when the SHOUTcast Server should give up waiting for a source -(mainly a relay server) to stream content from. 30-60 should be reasonable -enough values for this. +(mainly a relay server) to stream content from. Anywhere from 30 to 60 should be +a reasonable value for this. </p> <pre caption="Setting up the content directory"> <comment>; ContentDir specifies the directory location on disk of where to stream -; on-demand content from. Subdirectories are supported as of DNAS 1.8.2. +; on-demand content from. Subdirectories are supported as of DNAS 1.8.2. ; Default is ./content/, meaning a directory named content in the same directory ; as where sc_serv was invoked from.</comment> ContentDir=/opt/SHOUTcast/content/ </pre> <p> -The ContentDir specifies where to put on demand content. For example, if you +The ContentDir specifies where to put on demand content. For example, if you wish to stream an announcement to employees, you could use this for that -purpose. The SHOUTcast Server ebuild sets this to -<path>/opt/SHOUTcast/content</path> for you. To use this, put an mp3 in the +purpose. The SHOUTcast Server ebuild sets this to +<path>/opt/SHOUTcast/content</path> for you. To use this, put an mp3 in the content directory, then point your browser to -<c>http://example.com:[port]/content/mp3name.pls</c>. SHOUTcast Server will -autmatically create a streaming media compatible playlist for the mp3, and -stream it on demand. Use this as an alternative to SHOUTcast Trans for +<c>http://example.com:[port]/content/mp3name.pls</c>. SHOUTcast Server will +automatically create a streaming media compatible playlist for the mp3, and +stream it on demand. Use this as an alternative to SHOUTcast Trans for streaming media source. </p> @@ -412,7 +416,7 @@ hear this file played. As it states, the stream bitrate and the intro song bitrate must match, or else things will break. You can, however, put something such as intro128.mp3 and intro64.mp3, and it will play intro128.mp3 -to users connecting to a 128kbps stream, and intro64 users connecting at 64kbps. +to users connecting to a 128kbps stream, and intro64 for users connecting at 64kbps. </p> <pre caption="Setting up a back file"> @@ -483,7 +487,7 @@ </pre> <p> -AllowRelay determines of other servers are allowed to relay your content. +AllowRelay determines if other servers are allowed to relay your content. If you don't think you'll ever relay at all, set this to No. </p> @@ -497,7 +501,7 @@ -- [email protected] mailing list
