Paul Alfille-2 wrote:
>
> The statistics are usually generated by 1-wire trasmisssion errors: CRC
> errors and the like.
>
So disconnected devices which are polled will not generate errors counted
within the statistics, right?
Paul Alfille-2 wrote:
>
> Why not run owserver with --debug when you provoke your problem? the debug
> messages are the most comprehensive since they are what is actually used
> to
> fix owfs development bugs.
>
The provoked problem is not what I'm searching ;-)
Basicaly I try to fing a highly sporadic problem with DS18B20 connected via
a long cable to a USB-Busmaster. I
They work fine wit a polling rate of 10s for one or more weeks, suddenly
they disappear, al together at exactly the same time. But I can't provoke
this problem, I even hav bad access to the hardware, it's not easy to make
some changes.
I only have full remote access to the Linux/commandline, so I tried to find
it via analyzing the logs. But --debug throws so much logs, that I can't see
the problem after some hours... :-(
Paul Alfille-2 wrote:
>
> P.S. A longer term project to have a better error reporting mechanism for
> owcapi is under way.
>
This is good news!!! Thanks for all your time and energy
Achim
--
View this message in context:
http://old.nabble.com/How-to-enable-statistics--tp33194069p33198784.html
Sent from the OWFS - Dev mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
