On Mon, Feb 23, 2009 at 5:51 PM, David Baelde <[email protected]> wrote:
> On Mon, Feb 23, 2009 at 4:45 PM, Romain Beauxis <[email protected]> wrote:
>>> I see this error: "Thread 3 killed on uncaught exception Shout.No_login"
>>> and I need to restart it "liquidsoap /etc/liquidsoap/librecultivo.liq"...
>>
>> Ok, so what the logs tell you is that the connection was killed. I don't know
>> if this is good or bad, and it is probably also up to your usage.
>
> This is the normal thing to see when you use output.icecast(..)
> without overriding the default restart=false. If liquidsoap looses
> connectivity with icecast (network problem, or icecast shutdown, or
> kick) then it tries only once to reconnect, after 3s. If that attempt
> fails it "crashes" -- but in a clean way.
>
> If you use output.icecast.whatever(restart=true,...) the output will
> keep attempting to reconnect, never crashing liquidsoap. This is very
> often what you want. It's not the default only because it makes it
> tricky to detect typos in your script (host, password, etc): with
> restart=true, liq won't report the error immediately, and instead will
> silently, repeatedly fail to connect.

Thanks a lot David and Romain!

I have added restart=true, and will erase it before making tests with
my .liq file...


another question related to the way of compile it...

it is ok to use "--with-user=root --with-group=root"?
instead liquidsoap user/group?

that mean that liquidsoap will have root "powers"?


luciano

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users

Reply via email to