Re: [Savonet-users] Strange startup behavior - LS 1.0.0{SOLVED]

[<liq...@ao...>]

Oh my, do I feel stupid or what. I knew there was a file I hadn't  
configured yet - that was the one.
So sorry for bothering the list :(

Thanks,
kronos


On Wed, 28 Mar 2012 13:19:01 -0400, Peter Retep <pet...@gm...> wrote:

> Hi kronos,
>
> could you send the script to the mail list?
>
> /usr/local/etc/rc.d/liquidsoap
>
> So one could have a chance to check this.
>
> Thanks, Peter
>
>
> Am 27.03.2012 13:19, schrieb liq...@ao...:
>> On Wed, 28 Mar 2012 05:58:51 -0400, Mykola Dzham<i...@le...>  wrote:
>>
>>>   liq...@ao... wrote:
>>>> I'm getting strange behavior starting LS after upgrading from 0.92 to
>>>> 1.0.0.
>>> echo 'liquidsoap_config="/usr/local/etc/liquidsoap/liquidsoap.liq"'>>
>>> /etc/rc.conf
>>>
>>>> /usr/local/etc/rc.d/liquidsoap start
>>>> Starting liquidsoap.
>>>> Password:
>>>> su: Sorry
>>>> /usr/local/etc/rc.d/liquidsoap: WARNING: failed to start liquidsoap
>>> Probably you are try to run startup script from regular user, not from
>>> root
>>>
>> Trying it as root;
>>
>> /usr/local/etc/rc.d/liquidsoap start
>> Starting liquidsoap.
>> Line 1, char 2 before "/": Parse error!
>> /usr/local/etc/rc.d/liquidsoap: WARNING: failed to start liquidsoap
>>
>> This is the same strange result I got two year ago when I first tried  
>> LS,
>> but I can't recall how I fixed it. I will get the same error message
>> involving the '#!
>>   from the first line of my liquidsoap.liq script
>> (#!/usr/local/bin/liquidsoap). I normally run this script from regular
>> user 'rcr' via crontab, and it worked flawlessly for a year.
>>
>> My feeling is that the owner/group perms might be messed up.
>>
>> Current files:
>>
>> /usr/local/bin/liquidsoap, /usr/local/etc/liquidsoap are rot:wheel 555  
>> and
>> /usr/local/etc/rc.d/liquidsoap root:wheel 755.
>> All other files that liquidsoap would access (show files, etc) are owned
>> by rcr:wheel with appropriate perms.
>>
>> Unless I can resolve the hash-bang issue, the station will remain  
>> offline.
>> I just don't know where to look to begin resolving the problem.
>>
>> Any ideas?
>>
>> Thanks,
>> kronos
>>
>


-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/