Hi Paul, On 09/01/2010 06:57 AM, Paul Alfille wrote:
> Does this happen if you are reading the "fake" directory instead of a > real bus? I'm trying to distinguish between a cache problem and a FUSE > problem. Pardon the ignorance but how do I read from the "fake" directory instead of a real bus? Or asked another way, where are the "fake" directory and the real bus? I have: $ mount [...] OWFS on /owfs type fuse.OWFS (rw,nosuid,nodev,allow_other) Doing "ls /owfs" yields: $ ls /owfs bus.0 settings statistics structure system uncached Doing "ls /owfs" a second time shows all my sensors + a new "alarm" directory: $ ls /owfs 28.0B1DA2020000 28.4C0AA2020000 28.A049A2020000 28.CE489C020000 alarm simultaneous system 28.154BA2020000 28.4E09A2020000 28.B153A1020000 28.D622A2020000 bus.0 statistics uncached 28.3F2CA2020000 28.6618A2020000 28.B844A2020000 28.EC30A2020000 settings structure Cheers, Eloy Paris.- > > On Fri, Aug 27, 2010 at 4:53 PM, Eloy Paris <[email protected] > <mailto:[email protected]>> wrote: > > Hello, > > I've seen this a few times... after some amount of inactivity, i.e. > nobody reading from the owfs-mounted directory for some time, the first > attempt to read from a file in the owfs-mounted directory fails: > > $ for i in 28.*; do cat /owfs/$i/temperature; done; echo > cat: /owfs/28.*/temperature: No such file or directory > > Doing the same thing right after the failure does work. > > Not sure it happens every time there is inactivity. > > Is this normal behavior? > > Cheers, > > Eloy Paris.- > ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
