Hi Kris,
If you see the init.d launching the script without reporting an error,
it should mean that liquidsoap interpreted the script correctly.
Something probably stopped it from running soon after that, upon
startup: I'd guess either a problem on the log file, or on the telnet
server port.
In any case, the best is to run it by hand, possibly adding -v or
--debug, to see what's going on first. For the log file, I don't think
there is a way for a user to know where liquidsoap will put it (we
should fix this) but you can override it using
set("log.file.path","yourchoice").
Be aware that the init.d script launches your scripts using a special
liquidsoap user, who should have sufficient rights on relevant
directories.
HTH
--
David
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
