G'Day,
> Well, the goal is that no network packets can crash owserver, so let
> me chase this down.
I have been tracing this and have found the exact line where it
crashes. ow_locks.c, line 89, pn->ft is NULL and as such, when it is
used, it causes the crash. I can provide the full cont
Well, the goal is that no network packets can crash owserver, so let me
chase this down.
You are the world's expert on OMAP and OWFS. Are you maintaining that
adapter code yourself? Where can it be found? Perhaps, if it's ready, it can
be included in OWFS and thus track changes in the library.
Y
G'Day,
> If by path you mean something like "/10.23AD234523/temperature" the
> answer is simple:
> You use "get" for the root path ("/" or actually just "") and build
> from there.
I had actually tried that before, curious to what would happen rather
than expecting it to be the answer to
If by path you mean something like "/10.23AD234523/temperature" the answer
is simple:
You use "get" for the root path ("/" or actually just "") and build from
there.
The explanations for what devices support what properties, their format,
function, measurement units, etc is in the man files. Tha
G'Day,
I have been trying to create a owlua using owcapi as a basis. As far
as this is concerned, it has been a success --- I have an exact
equivalent to owcapi that can now be used from Lua. I just cannot make
any use of it! I can use the OW_init() and OW_finish() equivalent
functions
On 12/13/06, Matthew Percival <[EMAIL PROTECTED]> wrote:
G'Day,
I am looking to create a Lua interface to owlib --- effectively
owlua.
I would need to do this as a simple C library that makes the appropriate
calls, however, I have not been able to find any documentation that
would help
G'Day,
I am looking to create a Lua interface to owlib --- effectively owlua.
I would need to do this as a simple C library that makes the appropriate
calls, however, I have not been able to find any documentation that
would help with this. owcapi seems like it would be something similar
