Re: [Owfs-developers] owserver and owcapi behave differently with —enet device

2017-11-08 Thread Justin Brewer
Sorry for the multiple replies. I thought my messages weren't going out, but really there's just a 1h+ delay... On 11/08/2017 06:37 PM, Justin Brewer wrote: ...snip... -- Check out the vibrant tech community on one of

Re: [Owfs-developers] owserver and owcapi behave differently with —enet device

2017-11-08 Thread Justin Brewer
On Wed, Nov 08, 2017 at 01:51:49PM -0800, Andrew Brownsword wrote: > Nothing but crickets — is anyone out there? > > I’ve been poking at the code to try and figure out how to enable my debugger > to step into the libowcapi/libow code, but the make process is obscure enough > that some advice w

Re: [Owfs-developers] owserver and owcapi behave differently with —enet device

2017-11-08 Thread Justin Brewer
I have been working with libowcapi recently, and have seen similair symptoms. There's a race condition in libow that, if it doesn't outright crash, causes problems with directory listings. I have a patch for this issue here: https://gitlab.com/justinbrewer/owfs/commit/0234a2cecb56d0b6ca4d20a61

Re: [Owfs-developers] owserver and owcapi behave differently with —enet device

2017-11-08 Thread Jan Kandziora
Am 08.11.2017 um 22:51 schrieb Andrew Brownsword: > Nothing but crickets — is anyone out there? > > I’ve been poking at the code to try and figure out how to enable my > debugger to step into the libowcapi/libow code, but the make process > is obscure enough that some advice would be welcome... >

Re: [Owfs-developers] owserver and owcapi behave differently with —enet device

2017-11-08 Thread Andrew Brownsword
Nothing but crickets — is anyone out there? I’ve been poking at the code to try and figure out how to enable my debugger to step into the libowcapi/libow code, but the make process is obscure enough that some advice would be welcome... Sent from my iPhone > On Oct 31, 2017, at 3:11 PM, Andr