[Olsr-dev] Lockfile naming bug in 0.9.x

[Ferry Huberts]

Blast.

I fixed those in the previous jsoninfo/txtinfo fixes right before I 
refactored those into the patches that I committed :-(

Sorry for the crashes, the sgw changes were quite extensive and we 
didn't run into these crashes on our network.

Anyway, I've pushed the fixes.
Could you please test them again?



On 19/06/15 15:53, Malte wrote:
> On Fri, 19 Jun 2015, Ferry Huberts wrote:
>
>> The attached patch should fix the issue, please try it and report back.
>
> Thanks, it works as far as the lockfile is concerned.
>
> However, olsrd (still) segfaults as soon as I access the OLSR info page
> in LuCI. Doing "telnet localhost 9090", "GET /" triggers the segfault as
> well. Unfortunately, on that machine I don't have gdb or strace or similar.
>
> You can find the OLSRd config at http://pastebin.com/BSRbqxuU
>
> In case it matters - that node does not provide a SGW endpoint (it does
> not have a LAN uplink). It sees two other OLSR nodes, one of which
> provides an uplink.
>
> Best,
> Malte

-- 
Ferry Huberts