#35: RID leak ?
-------------------------+--------------------------------------------------
Reporter: toots | Owner: admin
Type: Bugs | Status: new
Priority: 7 | Milestone: 0.3.4
Component: Liquidsoap | Version: 0.3.3+svn
Resolution: | Keywords:
-------------------------+--------------------------------------------------
Changes (by mrpingouin):
* summary: No available RID ! => RID leak ?
Comment:
There was already a configuration key for that, but it was not attached to
the root configuration node. I just fixed that.
Regarding the default value set by the configure script, I think it's high
enough. After all, you are the monster user, you should be the one having
to override the default :) On the other hand, it doesn't cost much to
raise it: a higher value simply means that destroyed requests are kept
longer for post-mortem analysis (trace and metadata remain available but
the temporary files are already destroyed).
More interestingly, I think we may have a real bug here: I don't see why
it would loop forever on the fallback jingle. It should happen only
momentarily if there is no available RID, but I don't think this should
last... is there a leak somewhere ?
(So, another argument for not raising the value: it would just hide the
bug.)
--
Ticket URL: <http://savonet.rastageeks.org/ticket/35#comment:1>
Savonet <http://savonet.rastageeks.org/>
Let's program our stream !
