Am 17.05.2015 um 11:21 schrieb Henry:
>
> The "owdir /" by owserver of my raspberian Raspberry is too slow and
> sometimes blind, it not see first 1w-device (in a list by abc) always and
> show next 1w-devices after long time.
>
Having a device listed in / does not mean it is connected to the bus nor
does having a device *not listed* there means it is *not* connected to
the bus. This is because / is accessing the cache, which is not updated
automatically.
Use /uncached/ to immediately scan for all chips on the bus. The cached
list at / is updated in the process.
> I've got a list of
> devices by "ls" command of /sys/bus/w1/devices/ dir. All of my devices are
> listed.
>
The w1 kernel subsystem maintains it's own device list cache, which is
independend of the owfs cache. Same game as with the owfs cache, though
the kernel *automatically* updates its device list if not explicitely
told to keep quiet on the bus.
> Yet, the owserver work quick, good and stable with "owdir /xx.xxxxxxxxx"
> like comand.
>
This is accessing the cache, too. But the time before these values fade
away may be different from the time when the directory entry fades away.
Please, when debugging possible bus problems, always bypass the cache by
using the /uncached/ nodes instead of the plain ones.
Kind regards
Jan
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
