swift 05/06/30 09:27:11 Modified: xml/htdocs/doc/en shoutcast-config.xml Log: Fix spelling mistakes, no content change
Revision Changes Path 1.11 +69 -69 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.11&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.11&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.10&r2=1.11&cvsroot=gentoo Index: shoutcast-config.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/shoutcast-config.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- shoutcast-config.xml 30 Jun 2005 07:48:33 -0000 1.10 +++ shoutcast-config.xml 30 Jun 2005 09:27:11 -0000 1.11 @@ -1,6 +1,6 @@ <?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.10 2005/06/30 07:48:33 fox2mike Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/shoutcast-config.xml,v 1.11 2005/06/30 09:27:11 swift Exp $ --> <guide link="shoutcast-config.xml"> <title>Streaming Radio With SHOUTcast</title> @@ -85,11 +85,11 @@ <p> This is where the maximum number of users is set. As the caption states, -it is foolish to setup 100 users on a 256kbs upload (This is what I have set, +it is foolish to setup 100 users on a 256kbps 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 bandwidth you are using though. Bandwidth -comes at quite a high price to ISP's and some will cut your account, fine you +comes at quite a high price to ISPs and some will cut your account, fine you high costs to makeup, or both. </p> @@ -116,7 +116,7 @@ <comment>; PortBase. This is the port number your server will run on. The ; value, and the value + 1 must be available. If you get a fatal error when ; 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 +; machine is running on the same port (telnet localhost port number -- if you ; get connection refused then you're clear to use that port). Ports less than 1024 ; may require root privileges on *nix machines. The default port is 8000.</comment> PortBase=8000 @@ -135,7 +135,7 @@ ; or empty to turn off logging. The default is ./sc_serv.log ; on *nix systems or sc_serv_dir\sc_serv.log on win32. ; Note: on win32 systems if no path is specified the location is -; in the same dir as the executable, on *nix systems it is in the +; in the same directory as the executable, on *nix systems it is in the ; current directory.</comment> LogFile=/var/log/SHOUTcast.log </pre> @@ -171,7 +171,7 @@ <p> 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 +to stdout as they happen in real time. However, because the log file does the same thing, I recommend using it instead. </p> @@ -188,7 +188,7 @@ </p> <pre caption="Setting up filesystem modification logging"> -<comment>; TchLog decides whether or not the DNAS logfile should track yp +<comment>; TchLog decides whether or not the DNAS log file should track yp ; directory touches. Adds and removes still appear regardless of ; this setting. ; Default is yes @@ -215,7 +215,7 @@ </pre> <p> -This specifies whether or not you want to log hits to the http server that +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 secure logging possible, but not recommended for home/casual users. </p> @@ -228,7 +228,7 @@ ; Default is Yes (enabled).</comment> W3CEnable=Yes -<comment>; W3CLog describes the name of the logfile for W3C logging. Default logfile is +<comment>; W3CLog describes the name of the log file for W3C logging. Default log file is ; sc_w3c.log, in the same directory wherever the DNAS gets started from.</comment> W3CLog=/dev/null </pre> @@ -277,12 +277,12 @@ a local network), or your external IP (for instance, 209.204.249.201, for streaming to a WAN, but not a LAN). In most cases, you can reach your own stream by using 127.0.0.1 instead of what is listed here. ANY lets your -SHOUTcast Server bind to all IP addresses on all avaliable interfaces. +SHOUTcast Server bind to all IP addresses on all available interfaces. </p> <pre caption="Setting proxy/yp.SHOUTcast.com port"> <comment>; Yport, port to connect to yp.SHOUTcast.com on. For people behind caching -; webproxies, change this to the alternate port (666 is what it might be, +; web proxies, change this to the alternate port (666 is what it might be, ; check www.SHOUTcast.com if you have problems). Otherwise, leave this at 80. ; We're actively working on re-opening port 666, but as of release the only ; working port is port 80.</comment> @@ -307,7 +307,7 @@ <p> 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. +host name. Use this for logging purposes to create a more detailed report. </p> <pre caption="Setting up relaying"> @@ -370,7 +370,7 @@ <pre caption="Setting up the source timeout"> <comment>; AutoDumpSourceTime specifies how long, in seconds, the source stream is ; allowed to be idle before the server disconnects it. 0 will let the source -; stream idle indefinately before disconnecting. The default is 30.</comment> +; stream idle indefinitely before disconnecting. The default is 30.</comment> AutoDumpSourceTime=30 </pre> @@ -395,7 +395,7 @@ <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 -automatically create a streaming media compatible playlist for the mp3, and +automatically create a streaming media compatible play list for the mp3, and stream it on demand. Use this as an alternative to SHOUTcast Trans for streaming media source. </p> @@ -403,18 +403,18 @@ <pre caption="Setting up an intro file"> <comment>; IntroFile can specify a mp3 file that will be streamed to listeners right ; when they connect before they hear the live stream. -; Note that the intro file MUST be the same samplerate/channels as the -; live stream in order for this to work properly. Although bitrate CAN -; vary, you can use '%d' to specify the bitrate in the filename +; Note that the intro file MUST be the same sample rate/channels as the +; live stream in order for this to work properly. Although bit rate CAN +; vary, you can use '%d' to specify the butyrate in the filename ; (i.e. C:\intro%d.mp3 would be C:\intro64.mp3 if you are casting at 64kbps). ; The default is no IntroFile ; IntroFile=c:\intro%d.mp3</comment> </pre> <p> -This allows you to configure an intro file. Everytime users connect, they'll -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 +This allows you to configure an intro file. Every time users connect, they'll +hear this file played. As it states, the stream butyrate and the intro song +butyrate 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 for users connecting at 64kbps. </p> @@ -424,9 +424,9 @@ ; and over again when the source stream disconnects. AutoDumpUsers must be ; 0 to use this feature. When the source stream reconnects, the listeners ; are rejoined into the live broadcast. -; Note that the backup file MUST be the same samplerate/channels as the -; live stream in order for this to work properly. Although bitrate CAN -; vary, you can use '%d' to specify the bitrate in the filename +; Note that the backup file MUST be the same sample rate/channels as the +; live stream in order for this to work properly. Although bit rate CAN +; vary, you can use '%d' to specify the bit rate in the filename ; (i.e. C:\backup%d.mp3 would be C:\backup32.mp3 if you are casting at 32kbps). ; The default is no BackupFile ; BackupFile=C:\intro%d.mp3</comment> @@ -457,7 +457,7 @@ </p> <pre caption="Setting up a URL format"> -<comment>; URLFormat specifies a format string for what url is sent to the listener. +<comment>; URLFormat specifies a format string for what URL is sent to the listener. ; Behaves like TitleFormat (see above). ; The default is no format string. ; URLFormat=http://www.server.com/redirect.cgi?url=%s</comment> @@ -477,7 +477,7 @@ <p> This specifies whether or not you want to be listed as a public server even if -your relay server/source plugin is listed as such. +your relay server/source plug-in is listed as such. </p> <pre caption="Allowing relaying"> @@ -506,7 +506,7 @@ </p> <pre caption="Setting MetaInterval"> -<comment>; MetaInterval specifies how often, in bytes, metadata sent. +<comment>; MetaInterval specifies how often, in bytes, meta data sent. ; You should really leave this at the default of 32768, but the option is ; provided anyway.</comment> MetaInterval=32768 @@ -553,7 +553,7 @@ <pre caption="Setting the Rip list"> <comment>; RipFile is the text file sc_serv reads and writes to/from -; for the list of client IPs which are *ALWAYS* permitted +; for the list of client IP addresses which are *ALWAYS* permitted ; to connect to this server (useful for relay servers). ; This file is automatically generated via the web -- [email protected] mailing list
