View previous topic :: View next topic |
Author |
Message |
robertut
Joined: 31 Aug 2007 Posts: 156
|
Posted: Wed May 14, 2008 5:59 am Post subject: unknown element "burst-on-connect" |
|
|
Is this value unsupported?
Code: |
...58.170 - admin [14/May/2008:07:55:31 +0200] "GET /admin/function.xsl HTTP/1.1" 200 1130 "http://stream001.radio.hu:8080/adminbar.html" "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727)" 0
...58.170 - - [14/May/2008:07:55:31 +0200] "GET /images/corner_bottomleft.jpg HTTP/1.1" 200 8253 "http://stream001.radio.hu:8080/admin/function.xsl?perform=updatecfg" "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727)" 0 |
Code: |
[2008-05-14 07:55:31] INFO event/ Re-reading XML
[2008-05-14 07:55:31] WARN cfgfile/ unknown element "burst-on-connect" parsing "limits"
[2008-05-14 07:55:31] WARN fserve/ Cannot open mime types file .\mime.types
[2008-05-14 07:55:31] INFO connection/ shutting down connection thread
[2008-05-14 07:55:31] INFO fserve/ checking for file /images/corner_bottomleft.jpg (./web/images/corner_bottomleft.jpg)
[2008-05-14 07:55:31] INFO connection/ connection thread finished
[2008-05-14 07:55:31] INFO source/ Applying mount information for "/mr6s.mp3"
[2008-05-14 07:55:31] INFO source/ Applying mount information for "/mr6p.mp3"
...
|
What does it mean, unknown element "burst-on-connect" parsing "limits"?
My settings are:
Code: |
<limits>
<clients>15000</clients>
<sources>50</sources>
<queue-size>1024000</queue-size>
<header-timeout>15</header-timeout>
<client-timeout>60</client-timeout>
<source-timeout>60</source-timeout>
<burst-on-connect>1</burst-on-connect>
<burst-size>131072</burst-size>
</limits> |
According to the documentation, <burst-on-connect> is still in use. |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Wed May 14, 2008 2:19 pm Post subject: |
|
|
I've added general warning messages for unknown elements when parsing the xml config, generally used for catching mistyped xml tags. In this case burst-on-connect was doing nothing so it was removed from the tags. In 2.3, this burst setting was just an alias for burst-size of either 64k or 0k depending whether it was true or not. The default for burst-size is still the same (64k). The warning can be ignored without issue.
karl. |
|
Back to top |
|
|
robertut
Joined: 31 Aug 2007 Posts: 156
|
Posted: Wed May 14, 2008 2:25 pm Post subject: |
|
|
Well the documentation is really outdated... anyway, if one wants to disable it, it sets burst size to 0? |
|
Back to top |
|
|
robertut
Joined: 31 Aug 2007 Posts: 156
|
Posted: Wed May 14, 2008 2:28 pm Post subject: |
|
|
How about client-timeout? The documentation says: "This does not seem to be used." However, no warning for unknown element appears for it. Is it correct, that it's not used, or is it really in use? |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Wed May 14, 2008 2:43 pm Post subject: |
|
|
actually it was always used, I guess no one had filled out the section. you shouldn't need to change it
karl. |
|
Back to top |
|
|
|