Thanks. Recompiled with 2.2 and everything’s quick and peppy. Thanks for the 
help Bogdan.

--
Steve Woolley
steve.wool...@me.com



> On May 30, 2016, at 5:25 AM, Bogdan-Andrei Iancu <bog...@opensips.org> wrote:
> 
> Hi Steve,
> 
> Please update from git and give it a try again (there were couple of small 
> fixes). Still, I recommend to go for 2.2 .
> 
> Regards,
>  Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> http://www.opensips-solutions.com <http://www.opensips-solutions.com/>
> On 27.05.2016 22:21, Steve Woolley wrote:
>> Am trying to run opensips on a raspberry pi OS:Raspbian (based on Debian 
>> Jessie).
>> 
>> Compiled successfully but take a looooooooong time to start up opensips. 
>> (35-45 minutes).
>> Shows the following in the log (during the long pause):
>>      DBG:tm:lock_initialize: lock initialization started
>> 
>> 
>> Bogan-Andrei Iancu has suggested this is probably due to "System V locking 
>> support”.
>> He suggested trying to set USE_PTHREAD_MUTEX or USE_POSIX_SEMS compile 
>> options.
>> However, both of these options fail on:
>> 
>> Compiling net/net_tcp.c
>> net/net_tcp.c: In function ‘tcpconn_new’:
>> net/net_tcp.c:844:7: error: used union type value where scalar is required
>>    if (c->write_lock) lock_destroy(&c->write_lock);
>>        ^
>> Makefile.rules:25: recipe for target 'net/net_tcp.o' failed
>> make: *** [net/net_tcp.o] Error 1
>> 
>> Anyone had any luck on setting these compile options and/or getting opensips 
>> (efficiently) running on a Raspberry Pi?
>> 
>> --
>> Steve Woolley
>> steve.wool...@me.com <mailto:steve.wool...@me.com>
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Users mailing list
>> Users@lists.opensips.org <mailto:Users@lists.opensips.org>
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users 
>> <http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
> 

_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to