API tools faq
paste
View difference between Paste ID: SS19L5qg and eEd9DB5M
SHOW: | | - or go back to the newest paste.
1-
<Root>
1+
<Logger>
2-
    <!-- This section contains information for configuring the server. -->
2+
  <Access>
3-
    <Server>
3+
	<!-- This section configures the server to send log msgs to a   -->
4-
        <!-- Enables or disables IP version 6.      -->
4+
	<!-- remote logging server. To enable this feature, set the     -->
5-
        <!-- Operating system network stack should be configured to support IPV6 to make this happend.   -->
5+
	<!-- "enable" attribute to true. You can choose the type of     -->
6-
        <!-- FMS automatically detects operating system configuration and this key can force FMS to use IPv4 in case of IPv6 is available. -->
6+
	<!-- connection to use by specifying the "type" attribute which -->
7-
        <NetworkingIPv6 enable="false"></NetworkingIPv6>
7+
	<!-- can be set to either "udp" or "tcp". Default is udp.       -->
8-
        <!-- FMS Auth Adaptor plug-in section  -->
8+
	<LogServer enable="false" type="udp">
9-
        <Auth>This data can be retrieved by FMS Auth Adaptor plug-in.			Please look Auth Adaptor sample for details.</Auth>
9+
		<!-- Specify the IP and port of the server to log to.       -->
10-
        <!-- This sections contains SSL configuration information.     -->
10+
		<!-- For example,                                           -->
11-
        <SSL>
11+
		<!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort>              -->
12-
            <!-- Specify the number of bytes of entropy to use for     -->
12+
		<HostPort></HostPort>
13-
            <!-- seeding the PRNG. You cannot specify anything less    -->
13+
14-
            <!-- than 8 bytes, and the default is 16. Entropy is a     -->
14+
		<!-- This is an identifier used to identify the server that -->
15-
            <!-- measure of randomness. The more entropy, the more     -->
15+
		<!-- the log came from. By default, this is the IP address  -->
16-
            <!-- random numbers from the PRNG will be.                 -->
16+
		<!-- of this server.                                        -->
17-
            <SSLRandomSeed>16</SSLRandomSeed>
17+
		<ServerID></ServerID>
18-
            <!-- Specifies how often to flush expired sessions from    -->
18+
19-
            <!-- server-side session cache.                            -->

19+
		<!-- This specifies how many lines to log before including  -->

20-
            <SSLSessionCacheGC>5</SSLSessionCacheGC>

20+
		<!-- the fields header again.                               -->

21-
            <!-- The following section configures the server to act as an  -->

21+
		<DisplayFieldsHeader>100</DisplayFieldsHeader>

22-
            <!-- SSL client (out-going SSL connections).			       -->

22+
	</LogServer>

23-
            <SSLClientCtx>

23+
24-
                <!-- This specifies whether or not to verify the cert that -->

24+
	<!-- Directory in which log files will be placed, by default they are       -->

25-
                <!-- is returned by the server being connected to. Cert    -->

25+
	<!-- placed in logs/ in the server installation directory.                  -->

26-
                <!-- verification is enabled by default. To disable cert   -->

26+
    <Directory>${LOGGER.LOGDIR}</Directory>

27-
                <!-- verification, specify false.                          -->

27+
28-
                <!-- WARNING!!! Disabling certificate verification can     -->

28+
	<!-- Access log file name, everything inside the square brackets will be    -->

29-
                <!-- result in a security hazard. Please be sure you know  -->

29+
	<!-- substituted.                                                           -->

30-
                <!-- what you are doing if you wish to disable this.       -->

30+
	<!-- Y represents Year, only YYYY is allowed                                -->

31-
                <SSLVerifyCertificate>true</SSLVerifyCertificate>

31+
	<!-- M represents Month, only M or MM are allowed                           -->

32-
                <!-- Specifies the name of a directory containing CA       -->

32+
	<!-- D represents Day, only D or DD are allowed                             -->

33-
                <!-- certificates. Each file in the directory must contain -->

33+
	<!-- N represents Version, there is no limit on number of N                 -->

34-
                <!-- only a single CA certificate, and the files must be   -->

34+
	<!-- The number of each letter represents number of digits, for example     -->

35-
                <!-- named by the subject name's hash, and an extension of -->

35+
	<!-- April in M is 4 and in MM is 04                                        -->

36-
                <!-- ".0".                                                 -->

36+
    <FileName>access.[NN].log</FileName>

37-
                <!-- Win32 Only: If this tag is empty, we will attempt to  -->

37+
38-
                <!-- find CA certs in the "certs" directory located at the -->

38+
    <!-- The time field in a log file can be either in utc or local time. The   -->

39-
                <!-- same level as the "conf" directory. The Windows cert  -->

39+
    <!-- setting here can be used to override the server-wide configuration,    -->

40-
                <!-- store can be imported into this directory by running  -->

40+
    <!-- see <Logging> in Server.xml.                                           -->

41-
                <!-- FMSMaster -console -initialize from the command line. -->

41+
    <Time></Time>

42-
                <SSLCACertificatePath></SSLCACertificatePath>

42+
43-
                <!-- Specifies the name of a file containing one or more   -->

43+
    <Rotation>

44-
                <!-- CA certificates in PEM format.                        -->

44+
      <!-- Maximum file size in kilobytes (1024 bytes)                          -->

45-
                <SSLCACertificateFile></SSLCACertificateFile>

45+
      <MaxSize>10240</MaxSize>

46-
                <!-- Specifies the maximum depth of the certificate chain  -->

46+
47-
                <!-- we are willing to accept. If a self-signed root cert  -->

47+
      <!-- Rotation Time, there are 2 types										-->

48-
                <!-- cannot be found within this depth, cert verification  -->

48+
      <!-- If type="daily", rotation only occurs every 24 hours, and the format -->

49-
                <!-- will fail. Default is 9.                              -->

49+
	  <!-- is hh:mm, for example 00:00 will rotates every midnight              -->

50-
                <SSLVerifyDepth>9</SSLVerifyDepth>

50+
      <!-- If type="duration", rotation occurs when the duration of the log 	-->

51-
                <!-- Specifies the ciphers to use. This ia a list of colon delimited  -->

51+
	  <!-- exceed a certain length, duration takes a number in minutes  		-->

52-
                <!-- components. A component can be a key exchange algorithm,         -->

52+
      <Schedule type="daily">00:00</Schedule>

53-
                <!-- authentication method, encryption method, digest type, or one of -->

53+
54-
                <!-- a selected number of aliases for common groupings. For a list of -->

54+
      <!-- Max number of log files to keep, files will be named access.01.log,  -->

55-
                <!-- components, please refer to the FMS documentation. Do not change -->

55+
      <!-- access.02.log, access.03.log etc.                                    -->

56-
                <!-- the default settings unless you know what you are doing.         -->

56+
      <History>5</History>

57-
                <SSLCipherSuite>ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH</SSLCipherSuite>

57+
58-
            </SSLClientCtx>

58+
      <!-- When it is time to rotate the log files and Rename is set to true,   -->

59-
        </SSL>

59+
      <!-- access.00.log will be renamed to access.01.log and access.01.log     -->

60-
        <!-- Configures UID and GID for all the server processes       -->

60+
      <!-- will be renamed to access.02.log and so on until it reach the        -->

61-
        <!-- In unix, all the server processes will switch from root   -->

61+
      <!-- maximum history.  Therefore, log file with the highest version       -->

62-
        <!-- to the UID and GID specified in this section for security -->

62+
      <!-- number keeps the oldest log history.                                 -->

63-
        <!-- reason.  If no UID and GID are specified, the server      -->

63+
      <!-- If Rename is set to false, a new log file will be created with the   -->

64-
        <!-- will be running as root.                                  -->

64+
      <!-- next available version when rotation occurs.  Therefore, log file    -->

65-
        <Process>

65+
      <!-- with the lowest version number keeps the oldest log history.         -->

66-
            <!-- Process user ID (unix only) -->

66+
      <!-- Default is true.                                                     --> 

67-
            <UID>${SERVER.PROCESS_UID}</UID>

67+
      <Rename>true</Rename>

68-
            <!-- Process group ID (unix only) -->

68+
    </Rotation>

69-
            <GID>${SERVER.PROCESS_GID}</GID>

69+
70-
        </Process>

70+
    <!-- The following describes which events to be logged. The various events  -->

71-
        <!-- This key controls who has read/write access to the shared object   -->

71+
    <!-- are as follows,                                                        -->

72-
        <!-- files and stream files in the server. The Mask is used by umask    -->

72+
    <!--    Event Name						Category                            -->

73-
        <!-- to set file creation mask.  By default, the mask is set to 017     -->

73+
    <!--    ==========						========                            -->

74-
        <!-- and the files are created with permission 0666.                    -->

74+
    <!--    1. connect-pending              session                             -->

75-
        <!-- 0666 & ~017 = 0660 = r w - r w - - - -, that means the owner of    -->

75+
    <!--    2. connect                      session                             -->

76-
        <!-- the server and all the users belonging to the same group as the    -->

76+
    <!--    3. disconnect                   session                             -->

77-
        <!-- owner will have read/write access to the files. This mask must be  -->

77+
    <!--    4. publish                      stream                              -->

78-
        <!-- a 3 digit octal format                                             -->

78+
    <!--    5. unpublish                    stream                              -->

79-
        <!-- This config node is for unix only.                                 -->

79+
    <!--    6. play                         stream                              -->

80-
        <Mask>017</Mask>

80+
    <!--    7. pause                        stream                              -->

81-
        <!-- This key contains information related to the licensing of -->

81+
    <!--    8. unpause                      stream                              -->

82-
        <!-- the server, such as how many connections are allowed, and -->

82+
    <!--    9. seek                         stream                              -->

83-
        <!-- various other things in the server license.               -->

83+
    <!--   10. stop                         stream                              -->

84-
        <LicenseInfo>${SERVER.LICENSEINFO}</LicenseInfo>

84+
    <!--   11. record                       stream                              -->

85-
        <!-- All license keys added or removed using admin console is inserted in this tag -->

85+
    <!--   12. recordstop                   stream                              -->

86-
        <LicenseInfoEx>SECRET :P</LicenseInfoEx>

86+
    <!--   13. server-start                 server                              -->

87-
        <!-- Configures the largest I/O read buffers that the server will use. -->

87+
    <!--   14. server-stop                  server                              -->

88-
        <!-- Larger buffers may give better performance for some uses, but at  -->

88+
    <!--   15. vhost-start                  vhost                               -->

89-
        <!-- the cost of higher memory usage.                                  -->

89+
    <!--   16. vhost-stop                   vhost                               -->

90-
        <ReadBufferSize>4096</ReadBufferSize>

90+
    <!--   17. app-start                    application                         -->

91-
        <!-- Configures Flash Media Admin Server -->

91+
    <!--   18. app-stop                     application                         -->

92-
        <AdminServer>

92+
    <!-- The desired events are specified as a semi-colon separated list.       -->

93-
            <!-- Details and configurations for different versions of RTMP		-->

93+
    <!-- Specifying * will log all events.                                      -->

94-
            <RTMP>

94+
95-
                <!-- RTMPE is the encrypted RTMP protocol covering both RTMPE and RTMPTE -->

95+
    <Events>connect;disconnect;play;pause;unpause;stop</Events>

96-
                <!-- This is enabled by default, setting enabled to "false will not	 -->

96+
97-
                <!-- allow these protocols on this adaptor				 -->

97+
98-
                <RTMPE enabled="true"></RTMPE>

98+
    <!-- The following describes what information gets logged for each event.   -->

99-
            </RTMP>

99+
    <!-- Not all fields make sense for all events in which case they will be    -->

100-
            <!-- Specifies IP address and port to bind to. The format  -->

100+
    <!-- empty in the log file. The possible fields are,                        -->

101-
            <!-- is [<ip>][:<port>]. The default is to bind to "any"   -->

101+
      <!--    1. x-event          Type of event                                   -->

102-
            <!-- available IP on port 1111.                            -->

102+
      <!--    2. x-category       Event category                                  -->

103-
            <HostPort>${SERVER.ADMINSERVER_HOSTPORT}</HostPort>

103+
      <!--    3. date             Date at which the event occurred                -->

104-
            <!-- Specifies the interface and port to listen on internally -->

104+
      <!--    4. time             Time at which the event occurred                -->

105-
            <!-- for connections from fmscore process.                    -->

105+
      <!--    5. tz               Time zone information                           -->

106-
            <IpcHostPort>localhost:11110</IpcHostPort>

106+
      <!--    6. x-ctx            event dependant context information             -->

107-
            <!-- Specifies how often (in sec.) to check for inactive sockets. -->

107+
      <!--    7. s-ip		          ip address[es] of the server                    -->

108-
            <SocketGC>60</SocketGC>

108+
      <!--    8. x-pid            server process id                               -->

109-
            <!-- Configures UID and GID for the admin server                          -->

109+
      <!--    9. x-cpu-load       cpu load                                        -->

110-
            <!-- In unix, all the admin server processes will switch from root        -->

110+
      <!--   10. x-mem-load       memory load (as reported in getServerStats)     -->

111-
            <!-- to the UID and GID specified in this section for security reason.    -->

111+
      <!--   11. x-adaptor        adaptor name                                    -->

112-
            <!-- If no UID and GID are specified, the server will be running as root. -->

112+
      <!--   12. x-vhost          vhost name                                      -->

113-
            <Process>

113+
      <!--   13. x-app	          application name                                -->

114-
                <!-- Process user ID (unix only) -->

114+
      <!--   14. x-appinst        application instance name                       -->

115-
                <UID>${SERVER.PROCESS_UID}</UID>

115+
      <!--   15. x-duration	      duration of an event/session                    -->

116-
                <!-- Process group ID (unix only) -->

116+
      <!--   16. x-status		      status code					                            -->

117-
                <GID>${SERVER.PROCESS_GID}</GID>

117+
      <!--   17. c-ip             client ip address                               -->

118-
            </Process>

118+
      <!--   18. c-proto          connection protocol - rtmp or rtmpt             -->

119-
            <!-- to display <elem name="x"> instead of <_x> in the http command -->

119+
      <!--   19. s-uri            uri of the fms application                      -->

120-
            <AdminElem>false</AdminElem>

120+
      <!--   20. cs-uri-stem      stem of s-uri                                   -->

121-
            <!-- This tag specifies to which admin connections we respond to.-->

121+
      <!--   21. cs-uri-query     query portion of s-uri                          -->

122-
            <!-- This is specified as a comma delimited list of              -->

122+
      <!--   22. c-referrer       uri of the referrer                             -->

123-
            <!-- hostnames, domain names, and full or partial ip address, as -->

123+
      <!--   23. c-user-agent     user agent                                      -->

124-
            <!-- well as the keyword "all" (no quotes required).             -->

124+
      <!--   24. c-client-id      client id                                       -->

125-
            <!-- For example:                                                -->

125+
      <!--   25. cs-bytes         bytes transferred from client to server         -->

126-
            <!-- <Allow>x.foo.com, foo.com, 10.60.1.133, 10.60</Allow> or    -->

126+
      <!--   26. sc-bytes         bytes transferred from server to client         -->

127-
            <!-- <Allow>all</Allow>                                          -->

127+
      <!--   27. c-connect-type   type of connection received by the server       -->

128-
            <Allow>all</Allow>

128+
      <!--   28. x-sname          stream name                                     -->

129-
            <!-- This tag specifies to which admin connections not to        -->

129+
      <!--   29. x-sname-query    query portion of stream uri                     -->

130-
            <!-- respond to. This is specified as a comma delimited list     -->

130+
      <!--   30. x-suri-query		  Same as x-sname-query						               	-->

131-
            <!-- of hostnames, domain names, and full or partial ip address, -->

131+
      <!--   31. x-suri-stem		  cs-uri-stem + x-sname + x-file-ext			       	-->

132-
            <!-- as well as the keyword "all" (no quotes required).          -->

132+
      <!--   32. x-suri			      x-suri-stem + x-suri-query						          -->

133-
            <!-- For example:                                                -->

133+
      <!--   33. x-file-name      Full file path of recorded stream               -->

134-
            <!-- <Deny>x.foo.com, foo.com, 10.60.1.133, 10.60</Deny> or      -->

134+
      <!--   34. x-file-ext       stream type (flv or mp3)                        -->

135-
            <!-- <Deny>all</Deny>                                            -->

135+
      <!--   35. x-file-size      stream size in bytes                            -->

136-
            <Deny></Deny>

136+
      <!--   36. x-file-length    stream length in seconds                        -->

137-
            <!-- Specifies the order to evaluate the Allow/Deny tags. This   -->

137+
      <!--   37. x-spos           stream position                                 -->

138-
            <!-- can be <Order>Deny,Allow</Order>, which means the request   -->

138+
      <!--   38. cs-stream-bytes  stream bytes transferred from client to server  -->

139-
            <!-- will be processed if not in <Deny> or in <Allow>. Or it can -->

139+
      <!--   39. sc-stream-bytes  stream bytes transferred from server to client  -->

140-
            <!-- be <Order>Allow,Deny</Order>, which means the request will  -->

140+
      <!--   40. x-service-name   name of the service providing the connection    -->

141-
            <!-- be processed if in <Allow> and not in <Deny>.               -->

141+
      <!--   41. x-sc-qos-bytes	  bytes transferred from server to client for quality of service	-->

142-
            <Order>Allow,Deny</Order>

142+
      <!--   42. x-comment	      Comments	                                      -->

143-
        </AdminServer>

143+
      <!-- The field specification is a semi-colon separated list of one or more  -->

144-
        <!-- Configures automatic disconnecting of idle clients. A client is -->

144+
    <!-- and the special key word * indicates that all fields are to be logged. -->

145-
        <!-- idle if it has not sent or received any application data for    -->

145+
    <!-- When customizing the fields to be logged, it is strongly recommended   -->

146-
        <!-- some time. Application data does not include low level control  -->

146+
    <!-- to always at least log the type, category, date and time fields.       -->

147-
        <!-- msgs such as the built-in server ping mechanism. This is meant  -->

147+
148-
        <!-- to clean up clients that, for example, are not playing or not   -->

148+
    <Fields>x-category;x-event;date;time;x-pid;c-ip;cs-bytes;sc-bytes;x-sname;sc-stream-bytes;x-file-size;x-file-length;x-status</Fields>

149-
        <!-- publishing a stream, etc. To enable this feature, set the       -->

149+
150-
        <!-- enable attribute to true. It is disabled by default. This can   -->

150+
	<!-- Delimiter is used to separate between fields                           -->

151-
        <!-- be overridden on a per-vhost basis. However, if disabled here,  -->

151+
	<!-- Recommended: tab or ' '. If no delimiter is specified, default is tab  -->

152-
        <!-- it is disabled for all vhosts. But if enabled here, vhosts can  -->

152+
	<!-- Not Recommended: '#', because it is used as comment tag in W3C format  -->

153-
        <!-- override it and disable it for that vhost. Vhosts can also      -->

153+
	<!-- Disallowed: ''', '"', '.', ':', '-', '\' and all alpha-numeric         -->

154-
        <!-- override the max idle time (for that vhost only).               -->

154+
	<!-- (a-z, A-Z, 0-9).  Character ':' and '-' are not allowed because ':' is -->

155-
        <!-- <CheckInterval> is not overridable and applies to all vhosts.   -->

155+
	<!-- used in the time field and '-' is used in the date field and fields    -->

156-
        <AutoCloseIdleClients enable="false">

156+
	<!-- with empty value.                                                      -->

157-
            <!-- How often to check for idle clients. Specified in seconds. -->

157+
    <Delimiter></Delimiter>

158-
            <!-- Default is to check every 60 sec. (1 min)                  -->

158+
159-
            <CheckInterval>60</CheckInterval>

159+
	<!-- This is an optional flag to control if the fields need to be quoted    -->

160-
            <!-- How long a client can be idle before it is disconnected. -->

160+
	<!-- when space or delimiter are found in the fields.  It can be set to     -->

161-
            <!-- Specified in seconds. Default is 3600 sec. (1 hr)        -->

161+
	<!-- enable or disable.  By default, it is set to disable                   -->

162-
            <MaxIdleTime>3600</MaxIdleTime>

162+
	<QuoteFields>disable</QuoteFields>

163-
        </AutoCloseIdleClients>

163+
164-
        <!-- Specifies max resource limits for the server. -->

164+
	<!-- This is an optional flag to control if the fields need to be escaped   -->

165-
        <ResourceLimits>

165+
	<!-- when unsafe characters are found in the fields.  It can be set to      -->

166-
            <FLVCache>

166+
	<!-- enable or disable.  By default, it is set to enable                   -->

167-
                <FileCheckInterval>120</FileCheckInterval>

167+
	<!-- Based on rfc1738, unsafe characters are space, <, >, ", #, %, {, }, |, -->

168-
                <!-- The maximum size of the FLV cache, in megabytes. -->

168+
	<!-- ^, ~, [, ], `                                                          -->	

169-
                <!-- The default is 500MB. -->

169+
	<EscapeFields>enable</EscapeFields>

170-
                <MaxSize>${SERVER.FLVCACHE_MAXSIZE}</MaxSize>

170+
171-
                <!-- How often to modified the access time of the FLV cache file in   -->

171+
  </Access>

172-
                <!-- the proxy server when the FLV is actively used by the server.    -->

172+
  <Diagnostic>

173-
                <!-- Specified in seconds.  Default is 1200 sec. (20 mins)            -->

173+
	<!-- Directory in which log files will be placed, by default they are       -->

174-
                <!-- Set value to -1 to disable the server from changing the access   -->

174+
	<!-- placed in logs/ in the server installation directory.                  -->

175-
                <!-- time.                                                            -->

175+
	<Directory>${LOGGER.LOGDIR}</Directory>

176-
                <UpdateAccessTimeInterval>1200</UpdateAccessTimeInterval>

176+
177-
                <!-- The maximum number of keyframes per FLV file in cache.  The      -->

177+
    <!-- The time field in a log file can be either in utc or local time. The   -->

178-
                <!-- cache is used to save the keyframes that are being generated     -->

178+
    <!-- setting here can be used to override the server-wide configuration,    -->

179-
                <!-- in the server when enhanced seeking is enabled.                  -->

179+
    <!-- see <Logging> in Server.xml.                                           -->

180-
                <!-- Default is 0 keyframe.                                           -->

180+
    <Time></Time>

181-
                <MaxKeyframeCacheSize>0</MaxKeyframeCacheSize>

181+
182-
            </FLVCache>

182+
	<Rotation>

183-
            <!-- Configures buffer for FLV recording -->

183+
	  <!-- Maximum file size in kilobytes (1024 bytes)                          -->

184-
            <RecBuffer>

184+
	  <MaxSize>10240</MaxSize>

185-
                <!-- Maximum number of messages that buffer holds before the messages -->

185+
186-
                <!-- are commited to FLV.  Default is 200, and minimum is 0           -->

186+
	  <!-- Rotation Time, there are 2 types										-->

187-
                <MaxNumberOfMessages>200</MaxNumberOfMessages>

187+
	  <!-- If type="daily", rotation only occurs every 24 hours, and the format -->

188-
                <!-- Maximum size of the buffer can grow before the messages are      -->

188+
	  <!-- is hh:mm, for example 00:00 will rotates every midnight              -->

189-
                <!-- commited to FLV. Specified in kilo bytes.  Default is 5 Mb       -->

189+
	  <!-- If type="duration", rotation occurs when the duration of the log 	-->

190-
                <MaxSize>5120</MaxSize>

190+
	  <!-- exceed a certain length, duration takes a number in minutes  		-->

191-
                <!-- Maximum gap between 2 adjacent messages when comparing the       -->

191+
	  <Schedule type="daily">00:00</Schedule>

192-
                <!-- message timestamps with the real time.  Server logs a warning    -->

192+
193-
                <!-- when the timestamps between 2 adjacent messages is bigger than   -->

193+
	  <!-- Max number of log files to keep, files will be named admin.01.log,   -->

194-
                <!-- the difference in real time + MaxTimestampSkew.                  -->

194+
	  <!-- admin.02.log, admin.03.log etc.                                      -->

195-
                <!-- MaxTimestampSkew is in millisecond and is disabled by default    -->

195+
	  <History>5</History>

196-
                <!-- To enable the warning, set value to positive value               -->

196+
197-
                <MaxTimestampSkew>-1</MaxTimestampSkew>

197+
	  <!-- When it is time to rotate the log files and Rename is set to true,   -->

198-
            </RecBuffer>

198+
	  <!-- admin.00.log will be renamed to admin.01.log and admin.01.log        -->

199-
            <!-- Monitor CPU usage every N seconds. -->

199+
	  <!-- will be renamed to admin.02.log and so on until it reach the         -->

200-
            <CPUMonitor>1</CPUMonitor>

200+
	  <!-- maximum history.  Therefore, log file with the highest version       -->

201-
            <!-- GC unused I/O threads every N minutes. -->

201+
	  <!-- number keeps the oldest log history.                                 -->

202-
            <ThreadPoolGC>20</ThreadPoolGC>

202+
	  <!-- If Rename is set to false, a new log file will be created with the   -->

203-
            <!-- GC global msg pool ever N seconds. -->

203+
	  <!-- next available version when rotation occurs.  Therefore, log file    -->

204-
            <MsgPoolGC>60</MsgPoolGC>

204+
	  <!-- with the lowest version number keeps the oldest log history.         -->

205-
            <!-- GC unused applications every N minutes. -->

205+
	  <!-- Default is true.                                                     --> 

206-
            <ApplicationGC>5</ApplicationGC>

206+
	  <Rename>true</Rename>

207-
            <!-- MAX FLV cache size : specified in percent of total physical memory on the system. -->

207+
	</Rotation>

208-
            <FLVCacheSize>10</FLVCacheSize>

208+
209-
            <!-- Specifies how often (in sec.) to check for inactive sockets. -->

209+
	<core>

210-
            <SocketGC>60</SocketGC>

210+
		<!-- This section configures the server to send log msgs to a   -->

211-
            <!-- Specifies how often (in min.) to gc the SSL session cache for outgoing SSL connections. -->

211+
		<!-- remote logging server. To enable this feature, set the     -->

212-
            <SSLSessionCacheGC>5</SSLSessionCacheGC>

212+
		<!-- "enable" attribute to true. You can choose the type of     -->

213-
            <!-- FMS provides connectors which allow application scripts to connect to other FMS server or. -->

213+
		<!-- connection to use by specifying the "type" attribute which -->

214-
            <!-- HTTP servers. This section configures the connector subsystem -->

214+
		<!-- can be set to either "udp" or "tcp". Default is udp.       -->

215-
            <Connector>

215+
		<LogServer enable="false" type="udp">

216-
                <!-- HTTP connector : Used for Flash remoting-->

216+
			<!-- Specify the IP and port of the server to log to.       -->

217-
                <HTTP>

217+
			<!-- For example,                                           -->

218-
                    <!-- For all thread configuration.                                                 -->

218+
			<!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort>              -->

219-
                    <!-- A value of 0 allocates the default number of threads.                         -->

219+
			<HostPort></HostPort>

220-
                    <!-- A value greater than 0 allocates the exact number of threads specified.       -->

220+
			

221-
                    <!-- A value less than 0 ties it to the number (N) of processors,                  -->

221+
			<!-- This is an identifier used to identify the server that -->

222-
                    <!--       -1 means 1xN threads                                                    -->

222+
			<!-- the log came from. By default, this is the IP address  -->

223-
                    <!--       -2 means 2xN threads etc.                                               -->

223+
			<!-- of this server.                                        -->

224-
                    <!--Minimum number threads used for processing connection requests. 0 = default = 2 -->

224+
			<ServerID></ServerID>

225-
                    <MinConnectionThreads>0</MinConnectionThreads>

225+
226-
                    <!-- Maximum number of threads that can be created for connection processing. 0 = use default (10) -->

226+
			<!-- This specifies how many lines to log before including  -->

227-
                    <MaxConnectionThreads>0</MaxConnectionThreads>

227+
			<!-- the fields header again.                               -->

228-
                    <!-- Max connections requests that can be pending. Connections will be rejected if queue size limit is reached. -->

228+
			<DisplayFieldsHeader>100</DisplayFieldsHeader>

229-
                    <!-- -1 = default = 1000. -->

229+
		</LogServer>

230-
                    <MaxConnectionQueueSize>-1</MaxConnectionQueueSize>

230+
	</core>

231-
                    <!-- Configures how to cache handles used for HTTP requests -->

231+
232-
                    <HandleCache>

232+
	<edge>

233-
                        <!-- Max number of handles to cache -->

233+
		<!-- This section configures the server to send log msgs to a   -->

234-
                        <MaxSize>100</MaxSize>

234+
		<!-- remote logging server. To enable this feature, set the     -->

235-
                        <!-- If no http requests have been made to a host for this long, -->

235+
		<!-- "enable" attribute to true. You can choose the type of     -->

236-
                        <!-- we will free some of the handles cached for this host. Time -->

236+
		<!-- connection to use by specifying the "type" attribute which -->

237-
                        <!-- is specified in minutes. Default is 10 minutes.             -->

237+
		<!-- can be set to either "udp" or "tcp". Default is udp.       -->

238-
                        <IdleTime>30</IdleTime>

238+
		<LogServer enable="false" type="udp">

239-
                        <!-- When gc'ing handles, we don't gc all the handles for a host -->

239+
			<!-- Specify the IP and port of the server to log to.       -->

240-
                        <!-- all at once. Instead, we trim a percentage of the cached    -->

240+
			<!-- For example,                                           -->

241-
                        <!-- handles. Specified as a number between 0 and 1. Default is  -->

241+
			<!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort>              -->

242-
                        <!-- 0.2 (20%).                                                  -->

242+
			<HostPort></HostPort>

243-
                        <TrimSize>0.2</TrimSize>

243+
			

244-
                        <!-- How often to gc idle handles. Specified in minutes. Default -->

244+
			<!-- This is an identifier used to identify the server that -->

245-
                        <!-- is 60 min.                                                  -->

245+
			<!-- the log came from. By default, this is the IP address  -->

246-
                        <GCInterval>60</GCInterval>

246+
			<!-- of this server.                                        -->

247-
                    </HandleCache>

247+
			<ServerID></ServerID>

248-
                </HTTP>

248+
249-
                <!-- RTMP connector : For server to server connections-->

249+
			<!-- This specifies how many lines to log before including  -->

250-
                <RTMP>

250+
			<!-- the fields header again.                               -->

251-
                    <!-- For all I/O  and connection threads processing. -->

251+
			<DisplayFieldsHeader>100</DisplayFieldsHeader>

252-
                    <!-- A value of 0 allocates the default number of threads (10).                    -->

252+
		</LogServer>

253-
                    <!-- A value greater than 0 allocates the exact number of threads specified.       -->

253+
	</edge>

254-
                    <!-- A value less than 0 ties it to the number (N) of processors,                  -->

254+
255-
                    <!--       -1 means 1xN threads                                                    -->

255+
	<master>

256-
                    <!--       -2 means 2xN threads etc.                                               -->

256+
		<!-- This section configures the server to send log msgs to a   -->

257-
                    <!--Minimum numnber threads in the pool for I/O operations. 0 = defualt value 2x processor -->

257+
		<!-- remote logging server. To enable this feature, set the     -->

258-
                    <MinIOThreads>0</MinIOThreads>

258+
		<!-- "enable" attribute to true. You can choose the type of     -->

259-
                    <!-- Maximum number of threads that can be created for I/O processing. -1 = use default (32) -->

259+
		<!-- connection to use by specifying the "type" attribute which -->

260-
                    <MaxIOThreads>32</MaxIOThreads>

260+
		<!-- can be set to either "udp" or "tcp". Default is udp.       -->

261-
                    <!-- Number of completion routine threads that for edge (on win32) I/O processing. -->

261+
		<LogServer enable="false" type="udp">

262-
                    <NumCRThreads>0</NumCRThreads>

262+
			<!-- Specify the IP and port of the server to log to.       -->

263-
                    <!--Minimum number threads used for processing connection requests. 0 = default = 1 -->

263+
			<!-- For example,                                           -->

264-
                    <MinConnectionThreads>0</MinConnectionThreads>

264+
			<!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort>              -->

265-
                    <!-- Maximum number of threads that can be created for connection processing. 0 = use default (5) -->

265+
			<HostPort></HostPort>

266-
                    <MaxConnectionThreads>0</MaxConnectionThreads>

266+
			

267-
                    <!-- Max connections requests that can be pending. Connections will be rejected if queue size limit is reached. -->

267+
			<!-- This is an identifier used to identify the server that -->

268-
                    <!-- -1 = default = 1000. -->

268+
			<!-- the log came from. By default, this is the IP address  -->

269-
                    <MaxConnectionQueueSize>-1</MaxConnectionQueueSize>

269+
			<!-- of this server.                                        -->

270-
                </RTMP>

270+
			<ServerID></ServerID>

271-
            </Connector>

271+
272-
            <Protocol>

272+
			<!-- This specifies how many lines to log before including  -->

273-
                <!-- RTMP protocol configuration -->

273+
			<!-- the fields header again.                               -->

274-
                <!-- For all I/O  and connection threads processing. -->

274+
			<DisplayFieldsHeader>100</DisplayFieldsHeader>

275-
                <!-- A value of 0 allocates the default number of threads (10).                    -->

275+
		</LogServer>

276-
                <!-- A value greater than 0 allocates the exact number of threads specified.       -->

276+
	</master>

277-
                <!-- A value less than 0 ties it to the number (N) of processors,                  -->

277+
278-
                <!--       -1 means 1xN threads                                                    -->

278+
	<admin>

279-
                <!--       -2 means 2xN threads etc.                                               -->

279+
		<!-- This section configures the server to send log msgs to a   -->

280-
                <RTMP>

280+
		<!-- remote logging server. To enable this feature, set the     -->

281-
                    <Edge>

281+
		<!-- "enable" attribute to true. You can choose the type of     -->

282-
                        <!--Minimum numnber threads in the pool for I/O operations. 0 = 2 x Number of processors -->

282+
		<!-- connection to use by specifying the "type" attribute which -->

283-
                        <MinIOThreads>0</MinIOThreads>

283+
		<!-- can be set to either "udp" or "tcp". Default is udp.       -->

284-
                        <!-- Maximum number of threads that can be created for I/O processing. 0 = use default ( 10) -->

284+
		<LogServer enable="false" type="udp">

285-
                        <MaxIOThreads>0</MaxIOThreads>

285+
			<!-- Specify the IP and port of the server to log to.       -->

286-
                        <!--Size of direct access socket table for quick lookup. -1 = default = 200 -->

286+
			<!-- For example,                                           -->

287-
                        <SocketTableSize>-1</SocketTableSize>

287+
			<!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort>              -->

288-
                        <!-- Number of overflow buckets if all slots in socket table are in use. -1 = use default (16) -->

288+
			<HostPort></HostPort>

289-
                        <SocketOverflowBuckets>-1</SocketOverflowBuckets>

289+
			

290-
                        <!-- The maximum number of connections per second the server will -->

290+
			<!-- This is an identifier used to identify the server that -->

291-
                        <!-- accept. NOTE: this is per listener. So if FMS has multiple   -->

291+
			<!-- the log came from. By default, this is the IP address  -->

292-
                        <!-- listeners configured (i.e. listening on multiple ports), the -->

292+
			<!-- of this server.                                        -->

293-
                        <!-- connection rate configured here will apply to each listener. -->

293+
			<ServerID></ServerID>

294-
                        <!-- Default is -1 which means connection throttling is disabled. -->

294+
295-
                        <MaxConnectionRate>-1</MaxConnectionRate>

295+
			<!-- This specifies how many lines to log before including  -->

296-
                    </Edge>

296+
			<!-- the fields header again.                               -->

297-
                    <Core>

297+
			<DisplayFieldsHeader>100</DisplayFieldsHeader>

298-
                        <!--Minimum numnber threads in the pool for I/O operations. 0 = 2 x Number of processors -->

298+
		</LogServer>

299-
                        <MinIOThreads>0</MinIOThreads>

299+
	</admin>

300-
                        <!-- Maximum number of threads that can be created for I/O processing. 0 = use default ( 10) -->

300+
  </Diagnostic>

301-
                        <MaxIOThreads>0</MaxIOThreads>

301+
  <Application>

302-
                        <!--Size of direct access socket table for quick lookup. -1 = default = 200 -->

302+
	<!-- This section configures the server to send log msgs to a   -->

303-
                        <SocketTableSize>-1</SocketTableSize>

303+
	<!-- remote logging server. To enable this feature, set the     -->

304-
                        <!-- Number of overflow buckets if all slots in socket table are in use. -1 = use default (16) -->

304+
	<!-- "enable" attribute to true. You can choose the type of     -->

305-
                        <SocketOverflowBuckets>-1</SocketOverflowBuckets>

305+
	<!-- connection to use by specifying the "type" attribute which -->

306-
                    </Core>

306+
	<!-- can be set to either "udp" or "tcp". Default is udp.       -->

307-
                    <Admin>

307+
	<LogServer enable="false" type="udp">

308-
                        <!--Minimum numnber threads in the pool for I/O operations. 0 = 2 x Number of processors -->

308+
		<!-- Specify the IP and port of the server to log to.       -->

309-
                        <MinIOThreads>0</MinIOThreads>

309+
		<!-- For example,                                           -->

310-
                        <!-- Maximum number of threads that can be created for I/O processing. 0 = use default ( 10) -->

310+
		<!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort>              -->

311-
                        <MaxIOThreads>0</MaxIOThreads>

311+
		<HostPort></HostPort>

312-
                        <!--Size of direct access socket table for quick lookup. -1 = default = 200 -->

312+
		

313-
                        <SocketTableSize>-1</SocketTableSize>

313+
		<!-- This is an identifier used to identify the server that -->

314-
                        <!-- Number of overflow buckets if all slots in socket table are in use. -1 = use default (16) -->

314+
		<!-- the log came from. By default, this is the IP address  -->

315-
                        <SocketOverflowBuckets>-1</SocketOverflowBuckets>

315+
		<!-- of this server.                                        -->

316-
                    </Admin>

316+
		<ServerID></ServerID>

317-
                    <!-- Specifies the size (in bytes) of the socket send buffer. -->

317+
318-
                    <!-- Default is 0 which means to use OS default.              -->

318+
		<!-- This specifies how many lines to log before including  -->

319-
                    <SocketSndBuf>0</SocketSndBuf>

319+
		<!-- the fields header again.                               -->

320-
                    <!-- Specifies the size (in bytes) of the socket recv buffer. -->

320+
		<DisplayFieldsHeader>100</DisplayFieldsHeader>

321-
                    <!-- Default is 0 which means to use OS default.              -->

321+
	</LogServer>

322-
                    <SocketRcvBuf>0</SocketRcvBuf>

322+
	

323-
                </RTMP>

323+
	<!-- Directory in which log files will be placed, by default they are       -->

324-
                <!--Edge core communication protocol -->

324+
	<!-- placed in logs/ in the server installation directory.                  -->

325-
                <ECCP>

325+
	<Directory>${LOGGER.LOGDIR}</Directory>

326-
                    <!--Minimum numnber threads in the pool for I/O operations. 0 = 2 -->

326+
327-
                    <MinIOThreads>0</MinIOThreads>

327+
    <!-- The time field in a log file can be either in utc or local time. The   -->

328-
                    <!-- Maximum number of threads that can be created for I/O processing. 0 = use default (10) -->

328+
    <!-- setting here can be used to override the server-wide configuration,    -->

329-
                    <MaxIOThreads>0</MaxIOThreads>

329+
    <!-- see <Logging> in Server.xml.                                           -->

330-
                    <!--Size of direct access socket table for quick lookup. -1 = default = 200 -->

330+
    <Time></Time>

331-
                    <SocketTableSize>-1</SocketTableSize>

331+
332-
                    <!-- Number of overflow buckets if all slots in socket table are in use. -1 = use default (16) -->

332+
	<Rotation>

333-
                    <SocketOverflowBuckets>-1</SocketOverflowBuckets>

333+
	  <!-- Maximum file size in kilobytes (1024 bytes)                          -->

334-
                    <!-- Timeout (seconds) to detect unresponsive cores. 0 will disable timeout check. -->

334+
	  <MaxSize>10240</MaxSize>

335-
                    <CoreTimeout>30</CoreTimeout>

335+
336-
                </ECCP>

336+
	  <!-- Rotation Time, there are 2 types										-->

337-
                <!--Admin core communication protocol -->

337+
	  <!-- If type="daily", rotation only occurs every 24 hours, and the format -->

338-
                <ACCP>

338+
	  <!-- is hh:mm, for example 00:00 will rotates every midnight              -->

339-
                    <!--Minimum numnber threads in the pool for I/O operations. 0 = 2 -->

339+
	  <!-- If type="duration", rotation occurs when the duration of the log 	-->

340-
                    <MinIOThreads>0</MinIOThreads>

340+
	  <!-- exceed a certain length, duration takes a number in minutes  		-->

341-
                    <!-- Maximum number of threads that can be created for I/O processing. 0 = use default (10) -->

341+
	  <Schedule type="daily">00:00</Schedule>

342-
                    <MaxIOThreads>0</MaxIOThreads>

342+
343-
                    <!--Size of direct access socket table for quick lookup. -1 = default = 200 -->

343+
	  <!-- Max number of log files to keep, files will be named                 -->

344-
                    <SocketTableSize>-1</SocketTableSize>

344+
	  <!-- application.01.log, application.02.log etc.                          -->

345-
                    <!-- Number of overflow buckets if all slots in socket table are in use. -1 = use default (16) -->

345+
	  <History>5</History>

346-
                    <SocketOverflowBuckets>-1</SocketOverflowBuckets>

346+
347-
                </ACCP>

347+
	  <!-- When it is time to rotate the log files and Rename is set to true,   -->

348-
            </Protocol>

348+
	  <!-- application.00.log will be renamed to application.01.log and         -->

349-
            <IPCQueues>

349+
          <!-- application.01.log will be renamed to application.02.log and         -->

350-
                <!-- Controls the IPC msg queue used by all processes to communicate with each other. -->

350+
          <!-- so on until it reach the maximum history.  Therefore, log file with  -->

351-
                <GlobalQueue>

351+
          <!-- the highest version number keeps the oldest log history.             -->

352-
                    <!-- Max size (in Kb) of the shared memory heap used for this IPC msg queue. -->

352+
	  <!-- If Rename is set to false, a new log file will be created with the   -->

353-
                    <HeapSize>2048</HeapSize>

353+
	  <!-- next available version when rotation occurs.  Therefore, log file    -->

354-
                    <MaxQueueSize>10</MaxQueueSize>

354+
	  <!-- with the lowest version number keeps the oldest log history.         -->

355-
                </GlobalQueue>

355+
	  <!-- Default is true.                                                     --> 

356-
                <!-- Controls the IPC msg queue used by edge and core processes to communicate with each other. -->

356+
	  <Rename>true</Rename>

357-
                <EdgeCore>

357+
	</Rotation>

358-
                    <!-- Max size (in Kb) of the shared memory heap used for this IPC msg queue. -->

358+
  </Application>

359-
                    <HeapSize>1024</HeapSize>

359+
  <AuthEvent>

360-
                    <MaxQueueSize>10</MaxQueueSize>

360+
	<!-- This section configures the server to send log msgs to a   -->

361-
                </EdgeCore>

361+
	<!-- remote logging server. To enable this feature, set the     -->

362-
                <Services>

362+
	<!-- "enable" attribute to true. You can choose the type of     -->

363-
                    <!-- Max size (in Kb) of the shared memory heap used for this IPC msg queue. -->

363+
	<!-- connection to use by specifying the "type" attribute which -->

364-
                    <HeapSize>2048</HeapSize>

364+
	<!-- can be set to either "udp" or "tcp". Default is udp.       -->

365-
                    <MaxQueueSize>10</MaxQueueSize>

365+
	<LogServer enable="false" type="udp">

366-
                </Services>

366+
		<!-- Specify the IP and port of the server to log to.       -->

367-
            </IPCQueues>

367+
		<!-- For example,                                           -->

368-
            <MessageCache>

368+
		<!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort>              -->

369-
                <!-- Max free units in the cache. Note this may be less if "MaxSize" limit is reached -->

369+
		<HostPort></HostPort>

370-
                <MaxCacheUnits>4096</MaxCacheUnits>

370+
		

371-
                <!-- Max size of the cache in mega bytes. -->

371+
		<!-- This is an identifier used to identify the server that -->

372-
                <MaxCacheSize>100</MaxCacheSize>

372+
		<!-- the log came from. By default, this is the IP address  -->

373-
                <!-- Max message size thresold to get back into the cache. Specified in kilo bytes. -->

373+
		<!-- of this server.                                        -->

374-
                <MaxUnitSize>16</MaxUnitSize>

374+
		<ServerID></ServerID>

375-
                <!-- Value between 0 and 1 -->

375+
376-
                <FreeRatio>0.125</FreeRatio>

376+
		<!-- This specifies how many lines to log before including  -->

377-
                <!-- Value between 0 and 1 -->

377+
		<!-- the fields header again.                               -->

378-
                <GlobalRatio>0.4</GlobalRatio>

378+
		<DisplayFieldsHeader>100</DisplayFieldsHeader>

379-
                <!-- Max reuse count before freeing cache unit -->

379+
	</LogServer>

380-
                <MaxAge>1000000</MaxAge>

380+
381-
                <!-- Max reuse count before freeing cache unit -->

381+
	<!-- Directory in which log files will be placed, by default they are       -->

382-
                <UpdateInterval>1024</UpdateInterval>

382+
	<!-- placed in logs in the server installation directory.                  -->

383-
                <!-- Value between 0 and 1 -->

383+
    <Directory>${LOGGER.LOGDIR}</Directory>

384-
                <FreeMemRatio>0.5</FreeMemRatio>

384+
385-
            </MessageCache>

385+
	<!-- AuthEvent log file name, everything inside the square brackets will be -->

386-
            <SmallMemPool>

386+
	<!-- substituted.                                                           -->

387-
                <!-- Max free units in the cache. Note this may be less if "MaxSize" limit is reached -->

387+
	<!-- Y represents Year, only YYYY is allowed                                -->

388-
                <MaxCacheUnits>4096</MaxCacheUnits>

388+
	<!-- M represents Month, only M or MM are allowed                           -->

389-
                <!-- Max size of the cache in mega bytes. -->

389+
	<!-- D represents Day, only D or DD are allowed                             -->

390-
                <MaxCacheSize>100</MaxCacheSize>

390+
	<!-- N represents Version, there is no limit on number of N                 -->

391-
                <!-- Max message size thresold to get back into the cache. Specified in kilo bytes. -->

391+
	<!-- The number of each letter represents number of digits, for example     -->

392-
                <MaxUnitSize>16</MaxUnitSize>

392+
	<!-- April in M is 4 and in MM is 04                                        -->

393-
                <!-- Value between 0 and 1 -->

393+
    <FileName>authEvent.[NN].log</FileName>

394-
                <FreeRatio>0.125</FreeRatio>

394+
395-
                <!-- Value between 0 and 1 -->

395+
    <!-- The time field in a log file can be either in utc or local time. The   -->

396-
                <GlobalRatio>0.4</GlobalRatio>

396+
    <!-- setting here can be used to override the server-wide configuration,    -->

397-
                <!-- Max reuse count before freeing cache unit -->

397+
    <!-- see <Logging> in Server.xml.                                           -->

398-
                <MaxAge>1000000</MaxAge>

398+
    <Time></Time>

399-
                <!-- Max reuse count before freeing cache unit -->

399+
400-
                <UpdateInterval>1024</UpdateInterval>

400+
    <Rotation>

401-
                <!-- Value between 0 and 1 -->

401+
      <!-- Maximum file size in kilobytes (1024 bytes)                          -->

402-
                <FreeMemRatio>0.5</FreeMemRatio>

402+
      <MaxSize>10240</MaxSize>

403-
            </SmallMemPool>

403+
404-
            <LargeMemPool>

404+
      <!-- Rotation Time, there are 2 types										-->

405-
                <!-- Max free units in the cache. Note this may be less if "MaxSize" limit is reached -->

405+
      <!-- If type="daily", rotation only occurs every 24 hours, and the format -->

406-
                <MaxCacheUnits>4096</MaxCacheUnits>

406+
	  <!-- is hh:mm, for example 00:00 will rotates every midnight              -->

407-
                <!-- Max size of the cache in mega bytes. -->

407+
      <!-- If type="duration", rotation occurs when the duration of the log 	-->

408-
                <MaxCacheSize>100</MaxCacheSize>

408+
	  <!-- exceed a certain length, duration takes a number in minutes  		-->

409-
                <!-- Max message size thresold to get back into the cache. Specified in kilo bytes. -->

409+
      <Schedule type="daily">00:00</Schedule>

410-
                <MaxUnitSize>16</MaxUnitSize>

410+
411-
                <!-- Value between 0 and 1 -->

411+
      <!-- Max number of log files to keep, files will be named authEvent.01.log,  -->

412-
                <FreeRatio>0.125</FreeRatio>

412+
      <!-- authEvent.02.log, authEvent.03.log etc.                                 -->

413-
                <!-- Value between 0 and 1 -->

413+
      <History>5</History>

414-
                <GlobalRatio>0.4</GlobalRatio>

414+
415-
                <!-- Max reuse count before freeing cache unit -->

415+
      <!-- When it is time to rotate the log files and Rename is set to true,   -->

416-
                <MaxAge>1000000</MaxAge>

416+
      <!-- authEvent.00.log will be renamed to authEvent.01.log and             -->

417-
                <!-- Max reuse count before freeing cache unit -->

417+
      <!-- authEvent.01.log will be renamed to authEvent.02.log and so on until -->

418-
                <UpdateInterval>1024</UpdateInterval>

418+
      <!-- it reach the maximum history.  Therefore, log file with the highest  -->

419-
                <!-- Value between 0 and 1 -->

419+
      <!-- version number keeps the oldest log history.                         -->

420-
                <FreeMemRatio>0.5</FreeMemRatio>

420+
      <!-- If Rename is set to false, a new log file will be created with the   -->

421-
            </LargeMemPool>

421+
      <!-- next available version when rotation occurs.  Therefore, log file    -->

422-
            <SegmentsPool>

422+
      <!-- with the lowest version number keeps the oldest log history.         -->

423-
                <!-- Max free units in the cache. Note this may be less if "MaxSize" limit is reached -->

423+
      <!-- Default is true.                                                     --> 

424-
                <MaxCacheUnits>4096</MaxCacheUnits>

424+
      <Rename>true</Rename>

425-
                <!-- Max size of the cache in mega bytes. -->

425+
    </Rotation>

426-
                <MaxCacheSize>100</MaxCacheSize>

426+
427-
                <!-- Max message size thresold to get back into the cache. Specified in kilo bytes. -->

427+
    <!-- The following describes which events to be logged. The various events  -->

428-
                <MaxUnitSize>16</MaxUnitSize>

428+
    <!-- are as follows,                                                        -->

429-
                <!-- Value between 0 and 1 -->

429+
    <!--    Event Name						Category                            -->

430-
                <FreeRatio>0.125</FreeRatio>

430+
    <!--    ==========						========                            -->

431-
                <!-- Value between 0 and 1 -->

431+
    <!--    1. connect                      session                             -->

432-
                <GlobalRatio>0.4</GlobalRatio>

432+
    <!--    2. disconnect                   session                             -->

433-
                <!-- Max reuse count before freeing cache unit -->

433+
    <!--    3. publish                      stream                              -->

434-
                <MaxAge>1000000</MaxAge>

434+
    <!--    4. unpublish                    stream                              -->

435-
                <!-- Max reuse count before freeing cache unit -->

435+
    <!--    5. play                         stream                              -->

436-
                <UpdateInterval>1024</UpdateInterval>

436+
    <!--    6. pause                        stream                              -->

437-
                <!-- Value between 0 and 1 -->

437+
    <!--    7. seek                         stream                              -->

438-
                <FreeMemRatio>0.5</FreeMemRatio>

438+
    <!--    8. stop                         stream                              -->

439-
            </SegmentsPool>

439+
    <!--    9. filenametransform            stream                              -->

440-
            <Master>

440+
    <!--   10. loadsegment                  stream                              -->

441-
                <!-- How often to gc idle cores.                                             -->

441+
    <!--   11. app-start                    application                         -->

442-
                <CoreGC>300</CoreGC>

442+
    <!--   12. app-stop                     application                         -->

443-
                <!-- An idle core being gc'd is given at least this much to exit on its own. -->

443+
    <!--   13. action                       authorization                       -->				

444-
                <CoreExitDelay>20</CoreExitDelay>

444+
    <!-- The desired events are specified as a semi-colon separated list.       -->

445-
            </Master>

445+
    <!-- Specifying * will log all events.                                      -->

446-
            <Edge>

446+
447-
                <!-- Minimum number of threads per scheduler queue                  -->

447+
    <Events>app-start;connect;disconnect;play;pause;stop;filenametransform</Events>

448-
                <MinEventQueueThreads>2</MinEventQueueThreads>

448+
449-
                <!-- Maximum number of threads per scheduler queue                  -->

449+
450-
                <MaxEventQueueThreads>-2</MaxEventQueueThreads>

450+
    <!-- The following describes what information gets logged for each event.   -->

451-
                <!-- Number of scheduler queues         			    -->

451+
    <!-- Not all fields make sense for all events in which case they will be    -->

452-
                <NumSchedQueues>1</NumSchedQueues>

452+
    <!-- empty in the log file. The possible fields are,                        -->

453-
            </Edge>

453+
    <!--    1. x-event          Type of event                                   -->

454-
        </ResourceLimits>

454+
    <!--    2. x-category       Event category                                  -->

455-
        <!-- Overall logging configuration. This section contains only information that is  -->

455+
    <!--    3. x-eid            Event id                                        -->

456-
        <!-- that controls the overall logging behaviour. Specific logging configuration is -->

456+
    <!--    4. date             Date at which the event occurred                -->

457-
        <!-- located in Logger.xml.                                                         -->

457+
    <!--    5. time             Time at which the event occurred                -->

458-
        <Logging>

458+
    <!--    6. tz               Time zone information                           -->

459-
            <!-- The time field in a log file can be either in utc (gmt) or local (default).-->

459+
    <!--    7. x-ctx            event dependant context information             -->

460-
            <Time>local</Time>

460+
    <!--    8. x-pid            event id                                        -->

461-
            <!-- Logs recovery properies -->

461+
    <!--    9. x-adaptor        dll adaptor name                                -->

462-
            <!-- Retry number if open log failed. -->

462+
    <!--   10. x-vhost          vhost name                                      -->

463-
            <RetryNumber>0</RetryNumber>

463+
    <!--   11. x-app	        application name                                -->

464-
            <!-- Sleep interval in ms before retry  -->

464+
    <!--   12. x-appinst        application instance name                       -->

465-
            <RetrySleep>100</RetrySleep>

465+
    <!--   13. c-ip             client ip address                               -->

466-
            <!-- Number of records in log queue. If open log failed and queue has records >= this number core will be shutdown. -->

466+
    <!--   14. c-proto          connection protocol - rtmp or rtmpt             -->

467-
            <!-- -1 unlimited  -->

467+
    <!--   15. s-uri            uri of the fms application                      -->

468-
            <RecordsNumber>-1</RecordsNumber>

468+
    <!--   16. c-referrer       uri of the referrer                             -->

469-
            <!-- This controls the terminating characters of each log entry -->

469+
    <!--   17. c-user-agent     user agent                                      -->

470-
            <!-- CR = carriage return and LF = line feed.  Default is CRLF  -->

470+
    <!--   18. c-client-id      client id                                       -->

471-
            <TerminatingCharacters>CRLF</TerminatingCharacters>

471+
    <!--   19. cs-bytes         bytes transferred from client to server         -->

472-
            <Access>

472+
    <!--   20. sc-bytes         bytes transferred from server to client         -->

473-
                <!-- Whether access logging is enabled.                                     -->

473+
    <!--   21. x-sname          stream name                                     -->

474-
                <Enable>true</Enable>

474+
    <!--   22. x-file-size      stream size in bytes                            -->

475-
                <!-- The logging scope determines whether a log file is written out for     -->

475+
    <!--   23. x-file-length    stream length in seconds                        -->

476-
                <!-- each vhost or just one for the entire server. It may be either server  -->

476+
    <!--   24. x-spos           stream position                                 -->

477-
                <!-- or vhost.                                                              -->

477+
    <!--   25. cs-stream-bytes  stream reset param				-->

478-
                <Scope>server</Scope>

478+
    <!--   26. sc-stream-bytes  stream ignore param				-->

479-
            </Access>

479+
    <!--   27. s-ip		ip address[es] of the server                    -->

480-
            <Diagnostic>

480+
    <!--   28. x-duration	duration of an event/session                    -->

481-
                <!-- Whether diagnostic logging is enabled.                                 -->

481+
    <!--   29. x-status		status code					-->

482-
                <Enable>true</Enable>

482+
    <!--   30. cs-uri-stem      stem of s-uri                                   -->

483-
            </Diagnostic>

483+
    <!--   31. cs-uri-query     query portion of s-uri                          -->

484-
            <Application>

484+
    <!--   32. x-sname-query    query portion of stream uri                     -->

485-
                <!-- Whether application logging is enabled.                                -->

485+
    <!--   33. x-file-name      Fux-pidll file path of recorded stream          -->

486-
                <Enable>true</Enable>

486+
    <!--   34. x-file-ext       stream type (flv or mp3)                        -->

487-
            </Application>

487+
    <!--   35. c-connect-type   type of connection received by the server       -->

488-
            <AuthEvent>

488+
    <!--   36. x-service-name   name of the service providing the connection    -->

489-
                <!-- Whether logging is enabled.                                -->

489+
    <!--   37. x-comment	Comments	-->

490-
                <Enable>true</Enable>

490+
    <!-- The field specification is a semi-colon separated list of one or more  -->

491-
            </AuthEvent>

491+
    <!-- and the special key word * indicates that all fields are to be logged. -->

492-
            <AuthMessage>

492+
    <!-- When customizing the fields to be logged, it is strongly recommended   -->

493-
                <!-- Whether logging is enabled.                                -->

493+
    <!-- to always at least log the type, category, date and time fields.       -->

494-
                <Enable>true</Enable>

494+
      

495-
            </AuthMessage>

495+
    <Fields>x-category;x-event;date;time;x-app;x-appinst;c-ip;x-pid;x-status;x-adaptor;x-sname;x-file-length;x-spos;cs-stream-bytes;

496-
            <FileIO>

496+
	sc-stream-bytes;x-file-name;x-file-ext;x-file-size</Fields>

497-
                <!-- Whether logging is enabled.                                -->

497+
498-
                <Enable>true</Enable>

498+
499-
            </FileIO>

499+
	<!-- Delimiter is used to separate between fields                           -->

500-
        </Logging>

500+
	<!-- Recommended: tab or ' '. If no delimiter is specified, default is tab  -->

501-
        <!-- Server must reference itself locally, typically this is "localhost", but with more than one -->

501+
	<!-- Not Recommended: '#', because it is used as comment tag in W3C format  -->

502-
        <!-- Network Interface, "localhost" can map to an erroneous interface, thus the server will use	 -->

502+
	<!-- Disallowed: ''', '"', '.', ':', '-', '\' and all alpha-numeric         -->

503-
        <!-- the address listed here as the local loopback, default is "localhost"     			 -->

503+
	<!-- (a-z, A-Z, 0-9).  Character ':' and '-' are not allowed because ':' is -->

504-
        <Localhost>localhost</Localhost>

504+
	<!-- used in the time field and '-' is used in the date field and fields    -->

505-
        <!-- If system has more than 2 network ports, setup the public ip for the system  -->

505+
	<!-- with empty value.                                                      -->

506-
        <PublicIP></PublicIP>

506+
    <Delimiter></Delimiter>

507-
        <!-- SWFVerification configures how a SWF connecting to an app is verified.	-->

507+
508-
        <!-- This is for the Administrator level SWF Verification and is secondary  -->

508+
	<!-- This is an optional flag to control if the fields need to be quoted    -->

509-
        <!-- and independent of the Application level SWF Verification setups.  The -->

509+
	<!-- when space or delimiter are found in the fields.  It can be set to     -->

510-
        <!-- intended use is to put Administrator SWFs here that need to act as a   -->

510+
	<!-- enable or disable.  By default, it is set to disable                   -->

511-
        <!-- skeleton key (universal access) for apps needing SWF Verification      -->

511+
	<QuoteFields>disable</QuoteFields>

512-
        <!-- There is no override here of the Application level SWF Verification    -->

512+
513-
        <SWFVerification>

513+
	<!-- This is an optional flag to control if the fields need to be escaped   -->

514-
            <!-- Any SWFs found in this folder will be authenticated for connecting to any application	-->

514+
	<!-- when unsafe characters are found in the fields.  It can be set to      -->

515-
            <!-- on this server.  You can use a semicolon to seperate multiple directories here as well	-->

515+
	<!-- enable or disable.  By default, it is set to enable                   -->

516-
            <!-- For example C:\SWFs;D:\SWFs will allow swfs from either of these two directories to    -->

516+
	<!-- Based on rfc1738, unsafe characters are space, <, >, ", #, %, {, }, |, -->

517-
            <!-- be authenticated.                                                                      -->

517+
	<!-- ^, ~, [, ], `                                                          -->	

518-
            <SWFFolder></SWFFolder>

518+
	<EscapeFields>enable</EscapeFields>

519-
            <!-- This specifies the minimum accepted version of SWFVerification allowed by the server.	-->

519+
520-
            <!-- Initial version is 1; default is 0 which means to accept all forward versions.         -->

520+
  </AuthEvent>	

521-
            <MinGoodVersion></MinGoodVersion>

521+
  <AuthMessage>

522-
            <!-- SWFVerification data are cache in the server.  This configures how the cache behaves.  -->

522+
	<!-- This section configures the server to send log msgs to a   -->

523-
            <Cache>

523+
	<!-- remote logging server. To enable this feature, set the     -->

524-
                <!-- TTL is the time to live of each SWF in the cache.  Specified in minutes.       -->

524+
	<!-- "enable" attribute to true. You can choose the type of     -->

525-
                <!-- Default value is 1440 minutes (24 hours)                                       -->

525+
	<!-- connection to use by specifying the "type" attribute which -->

526-
                <TTL>1440</TTL>

526+
	<!-- can be set to either "udp" or "tcp". Default is udp.       -->

527-
                <!-- The maximum time to wait for the server to scan the SWF folders for updates    -->

527+
	<LogServer enable="false" type="udp">

528-
                <!-- when there is a miss in the cache.  Specified in minutes.  Default value is    -->

528+
		<!-- Specify the IP and port of the server to log to.       -->

529-
                <!-- 5 minutes.                                                                     -->

529+
		<!-- For example,                                           -->

530-
                <UpdateInterval>5</UpdateInterval>

530+
		<!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort>              -->

531-
            </Cache>

531+
		<HostPort></HostPort>

532-
        </SWFVerification>

532+
		

533-
    </Server>

533+
		<!-- This is an identifier used to identify the server that -->

534-
    <!-- Set this to the domain name of the server. It is used to set the hostname in -->

534+
		<!-- the log came from. By default, this is the IP address  -->

535-
    <!-- the referrer header tag when making a connection with a remote server using  -->

535+
		<!-- of this server.                                        -->

536-
    <!-- NetConnection. If empty the hostname field is empty in referrer header.      -->

536+
		<ServerID></ServerID>

537-
    <ServerDomain></ServerDomain>

537+
538-
</Root>
538+
		<!-- This specifies how many lines to log before including  -->

539
		<!-- the fields header again.                               -->

540
		<DisplayFieldsHeader>100</DisplayFieldsHeader>

541
	</LogServer>

542
543
	<!-- Directory in which log files will be placed, by default they are       -->

544
	<!-- placed in logs in the server installation directory.                  -->

545
	<Directory>${LOGGER.LOGDIR}</Directory>

546
547
    <!-- The time field in a log file can be either in utc or local time. The   -->

548
    <!-- setting here can be used to override the server-wide configuration,    -->

549
    <!-- see <Logging> in Server.xml.                                           -->

550
    <Time></Time>

551
552
	<Rotation>

553
	  <!-- Maximum file size in kilobytes (1024 bytes)                          -->

554
	  <MaxSize>10240</MaxSize>

555
556
	  <!-- Rotation Time, there are 2 types										-->

557
	  <!-- If type="daily", rotation only occurs every 24 hours, and the format -->

558
	  <!-- is hh:mm, for example 00:00 will rotates every midnight              -->

559
	  <!-- If type="duration", rotation occurs when the duration of the log 	-->

560
	  <!-- exceed a certain length, duration takes a number in minutes  		-->

561
	  <Schedule type="daily">00:00</Schedule>

562
563
	  <!-- Max number of log files to keep, files will be named                 -->

564
	  <!-- authMessage.01.log, authMessage.02.log etc.                          -->

565
	  <History>5</History>

566
567
	  <!-- When it is time to rotate the log files and Rename is set to true,   -->

568
	  <!-- authMessage.00.log will be renamed to authMessage.01.log and         -->

569
          <!-- authMessage.01.log will be renamed to authMessage.02.log and         -->

570
          <!-- so on until it reach the maximum history.  Therefore, log file with  -->

571
          <!-- the highest version number keeps the oldest log history.             -->

572
	  <!-- If Rename is set to false, a new log file will be created with the   -->

573
	  <!-- next available version when rotation occurs.  Therefore, log file    -->

574
	  <!-- with the lowest version number keeps the oldest log history.         -->

575
	  <!-- Default is true.                                                     --> 

576
	  <Rename>true</Rename>

577
	</Rotation>

578
  </AuthMessage>

579
  <FileIO>

580
	<!-- This section configures the server to send log msgs to a   -->

581
	<!-- remote logging server. To enable this feature, set the     -->

582
	<!-- "enable" attribute to true. You can choose the type of     -->

583
	<!-- connection to use by specifying the "type" attribute which -->

584
	<!-- can be set to either "udp" or "tcp". Default is udp.       -->

585
	<LogServer enable="false" type="udp">

586
		<!-- Specify the IP and port of the server to log to.       -->

587
		<!-- For example,                                           -->

588
		<!-- <HostPort>xxx.xxx.xxx.xxx:1234</HostPort>              -->

589
		<HostPort></HostPort>

590
		

591
		<!-- This is an identifier used to identify the server that -->

592
		<!-- the log came from. By default, this is the IP address  -->

593
		<!-- of this server.                                        -->

594
		<ServerID></ServerID>

595
596
		<!-- This specifies how many lines to log before including  -->

597
		<!-- the fields header again.                               -->

598
		<DisplayFieldsHeader>100</DisplayFieldsHeader>

599
	</LogServer>

600
601
	<!-- Directory in which log files will be placed, by default they are       -->

602
	<!-- placed in logs in the server installation directory.                  -->

603
	<Directory>${LOGGER.LOGDIR}</Directory>

604
605
    <!-- The time field in a log file can be either in utc or local time. The   -->

606
    <!-- setting here can be used to override the server-wide configuration,    -->

607
    <!-- see <Logging> in Server.xml.                                           -->

608
    <Time></Time>

609
610
	<Rotation>

611
	  <!-- Maximum file size in kilobytes (1024 bytes)                          -->

612
	  <MaxSize>10240</MaxSize>

613
614
	  <!-- Rotation Time, there are 2 types										-->

615
	  <!-- If type="daily", rotation only occurs every 24 hours, and the format -->

616
	  <!-- is hh:mm, for example 00:00 will rotates every midnight              -->

617
	  <!-- If type="duration", rotation occurs when the duration of the log 	-->

618
	  <!-- exceed a certain length, duration takes a number in minutes  		-->

619
	  <Schedule type="daily">00:00</Schedule>

620
621
	  <!-- Max number of log files to keep, files will be named                 -->

622
	  <!-- fileMessage.01.log, fileMessage.02.log etc.                          -->

623
	  <History>5</History>

624
625
	  <!-- When it is time to rotate the log files and Rename is set to true,   -->

626
	  <!-- fileMessage.00.log will be renamed to fileMessage.01.log and         -->

627
          <!-- fileMessage.01.log will be renamed to fileMessage.02.log and         -->

628
          <!-- so on until it reach the maximum history.  Therefore, log file with  -->

629
          <!-- the highest version number keeps the oldest log history.             -->

630
	  <!-- If Rename is set to false, a new log file will be created with the   -->

631
	  <!-- next available version when rotation occurs.  Therefore, log file    -->

632
	  <!-- with the lowest version number keeps the oldest log history.         -->

633
	  <!-- Default is true.                                                     --> 

634
	  <Rename>true</Rename>

635
	</Rotation>

636
  </FileIO>

637
</Logger>
        

    


            


                                


        

            



                
    

        Public Pastes
    

    
            

    

                    

        

    





    


    
    
    
    
    
    
    
    




    


    



                

            We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.             OK, I Understand
        

    
                

            

                
                    
                
            

            

                Not a member of Pastebin yet?

                Sign Up, it unlocks many cool features!