Hello, I set (dynamically) /settings/timeout/volatile to 300 seconds but doing successive "cat /owfs/<device address>/temperature" (a few seconds apart) still causes owserver to go out and fetch a new temperature sample (I think this is the case because the cat operation pauses a few seconds instead of printing data right away). I would have expected to get the same (cached) temperature for the next 300 seconds.
Am I misunderstanding the way /settings/timeout/volatile should work? Is there a good way to check that owserver is honoring the volatile timeout and that it is not going out to the bus to fetch new data? I am running 2.8p1 and my bus master is a LinkUSB. What I want to accomplish by changing /settings/timeout/volatile is to prevent a process from blocking while the temperature file is being read. Is there a better way than relying on the volatile timeout? I thought that caching would help me here. Cheers, Eloy Paris.- ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
