Well, the answer is that owfs shows both the true paths, and some "union" paths.
i.e:
owhttpd -> owserver -> usb -> DS18S20 (10.123123) is a typical setup.
The true (abbreviated) directory
statistics (owhttpd)
settings (owhttpd)
bus.0 -> statistics (owserver)
settings (owserver)
interface (tcp to owserver)
bus.0 -> statistics (usb)
settings (usb)
interface (usb)
10.123123 -> temperature...
The displayed directory ( abbreviated as well)
10.123123
bus.0 ->10.123123
statistics (owserver)
settings (owserver)
interface (tcp to owserver)
bus.0 ->10.123123
statistics (usb)
settings (usb)
interface (usb)
So when the error is a select on the usb bus master, the statistics
for it are /bus.0/bus.0/statistics
In short, you don't need to know anything about the actual topology to
use the 1-wire slaves. If you want to set or analyse your actual
network topology, then you must address your queries more exactly.
In this case I have a simple topology, but there can be multiple
connections at every stage, with bus.1, bus.2... possible. The
protocol does protect against loops, however. With some ingenuity, it
might be possible to have a bus-master appear twice. That is not
recommended.
On Tue, Feb 8, 2011 at 2:54 PM, nick <[email protected]> wrote:
> Can i ask why "bus.0" is in the path twice ? I hadn't noticed it before.
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
