Hey Paul and owfs team,
Has anyone seen the following behavior:
All tests done on FC9 stock install straight from DVD and fresh download
of the latest owfs tar.gz
If I use owserver and owfs then after about 5-6 hours of moderate volume
of calls to /mnt/1wire using basic bash scripts (cat commands to read
temperature once 2-3 seconds using the regular path, NOT the uncashed
path) owfs crashes and exists.
The error logged is always the same:
Aug 28 05:13:26 localhost kernel: owfs[17343]: segfault at 5415265c ip
0016a96c sp 54152650 error 6 in libow-2.7.so.4.0.0[12f000+53000]
Aug 29 05:07:20 localhost kernel: owfs[2388]: segfault at 52d8065c ip
0014c96c sp 52d80650 error 6 in libow-2.7.so.4.0.0[111000+53000]
Once owfs no longer runs due to the crash, further tests were done. At
that time owserver still continues to run happy and owhttpd also runs
AND returns real data from the 1wire network so the owfs crash is likely
NOT due to a lower layer irregularity (say if owserver crashes so will
the upper layers). Owhttpd returns real values which was tested by
synthetically inducing some sensors to change readings (blow dryer) and
observing whether owhttpd will show the changes and it does!
However if I ONLY use owfs and have it talk directly to ttyS0 then it is
100% stable and it never crashes
I am looking for similar experiences so it will help me figure out
what's wrong.
Thanks
~B
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers