On Sat, Feb 5, 2011 at 6:20 AM, Hyun-ki Chung hyunkich...@yahoo.com wrote:
BTW, the insert function loops on the last child, my promotion track
- fail() doesn't seem to work, while your alternative that merges everything
seems to work well in my case. That might be because I didn't understand
Hi Peter,
As you might suspect, it's hard to distinguish a short term failure
from a real unavailability, and it certainly can't be done at the
level of a fallback. Pretty much the only place to do this is when
setting buffering parameters.
I think you already know that and your goal is
Thanks very much for your help rodger, I have fixed the problem. More
details in http://dev.sourcefabric.org/browse/LS-473. If this seems
all good to you as well I'll definitively close the issue.
--
David
--
The
Hi David,
Of course you can distribite the scripts, I would feel honored.
As far as I understand upstart's exec method, it will fail as soon as the
executed command returns.
When I use liquidsoap's daemon mode upstart will respawn immediately after
starting daemon and give up after 10 attempts
2011/2/7 kro...@aolohr.com:
Hi,
Hi Andre,
To better understand some strange behaviour with output from my
switch-based program scheduling, I'd like to clarify exactly what
is the default behaviour in liquidsoap.
I use 'track_sensitive=false' to trigger an abrupt end of the
current
