Am 09.10.2015 um 21:17 schrieb Loren Amelang:
>
> --> My 14.04 system adds two values to the example shown on that
> page: ha7 60 w1 30
>
> No idea what ha7 is, but I assume w1 is a timeout for declaring that
> no response was received from the w1 mechanism, not a specification
> of how often to poll it for new temperatures.
>
These are connection retry values for various host controllers. ha7 is
an ethernet device so it's always there. w1 is there because you have
configured it.
>
> Apparently the Volatile = 15 second setting should control w1 reads.
> But my w1 reads the bus at 10.1 second intervals...
>
Again, the w1 kernel subsystem isn't exclusive to owfs, but various
other tools in your system may use it too. Especially polling the
temperature sensors, because they think they are vital for your system,
like battery or hard disk temperature.
>
> I've never had any luck changing any of the settings with httpd.
> Whenever I change an httpd value, the new value shows for a second or
> so, and then it changes itself right back!
>
Some values just aren't changeable. Some are not possible to be read
back, yet they have been changed. The way you have configured it,
owhttpd is just a web interface to owserver.
> The web page says, "The timeouts are read/writable values found under
> /settings/timeout/[volatile|stable|directory|presence]", but I can't
> find that path on my system.
>
This is a path inside the owfs system, not inside the root file system.
To pass this to owserver do e.g.
$ owwrite -s localhost:4304 /settings/timeout/volatile 30
owget is the corresponding read tool.
If you want to have these pseudo-paths mapped into the real filesystem
of your machine, for example for accessing it with echo and cat, you
have to use the "owfs" tool. I don't recommend it because it adds more
complexity to your machine and you gain very little from it.
$ mkdir /tmp/ow
$ owfs -s localhost:4304 /tmp/ow <- this one daemonizes itself
$ ls -al /tmp/ow/uncached
...
> Closest hit is:
> /sys/devices/w1_bus_master1/w1_master_timeout
>
This is configuring the w1 kernel driver directly. It has nothing to do
with owfs.
> Where is httpd getting those settings? Should they appear as "files"
> in the filesystem? Is there some other way for me to change them? And
> why doesn't my system seem to be following them?
>
Loren, please stop confusing owfs paths with filesystem paths.
Kind regards
Jan
------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
