Sorry if I was not clear enough… (and yes I should dump my mail client, it
keeps rewriting my mails inserting fancy utf-8 chars and http links).
On my owfs.conf I had these two lines:
server: link = /dev/ttyS0
server: server = some.fully.qualified.domain.name:4304
which mean that sensors at the root (owdir /) will be collected from a Link45
(see http://www.ibuttonlink.com/products/link45
<http://www.ibuttonlink.com/products/link45>) connected to local serial port
/dev/ttyS0 and the sensors from a remote owserver.
So I had
/bus.0/interface/settings/name -> LinkHub-E v1.1
/bus.0/interface/settings/address -> /dev/ttyS0
/bus.1/interface/settings/name -> tcp
/bus.1/interface/settings/address ->
some.fully.qualified.domain.name:4304
(note the bus.0 and bus.1 thing.) This resulted in the 40ms times…
After inserting the dotted quad instead of the domain name, things went on
smoothly… and I convinced myself it was a DNS lookup issue.
(but maybe this was not the real problem.) Maybe there is another factor
forcing a bus rescan on your setup at each dir command… (BTW when i I dir
/uncached/ times grow up to about 100ms.)
IMHO your config should be:
! server: server = localhost:4304
server: server = config for your bus masters
server: port = 4304
(localhost does no harm if you have the '127.0.0.1 localhost’ line in
/etc/hosts, and ‘hosts: files dns’ in /etc/nsswitch.conf, which should be the
default.)
S.
> On 09 Nov 2015, at 22:21, Loren Amelang <lo...@pacific.net> wrote:
>
> On Mon, 09 Nov 2015 15:46:48 +0100
> Stefano Miccoli mo...@icloud.com wrote:
>
>> Curiously I ran in a similar situation as the BBB:
> ...
>> ** non persistent : 39.96 ms, 39.99 ms, 40.00 ms, 40.01 ms, 40.21 ms,
>> ** persistent : 39.98 ms, 40.00 ms, 40.00 ms, 40.00 ms, 40.00 ms,
>
>> When I substitute the fqdn with the IP number I get
> ...
>> ** non persistent : 2.14 ms, 2.15 ms, 2.15 ms, 2.16 ms, 2.23 ms,
>> ** persistent : 1.90 ms, 1.92 ms, 1.94 ms, 1.95 ms, 1.96 ms,
>
>
> I've already inserted my BBB's numeric IP address into my /etc/owfs.conf, so
> I could connect to owserver from other machines:
> ---
> The localhost setting is in (at least) two places in /etc/owfs.conf:
> ! server: server = 10.1.1.4:4304
> # was previously localhost:4304
> And:
> server: port = 4304
> # was previously localhost:4304
> ---
>
>
> In Stefano's post:
> ---
> In fact the original configuration (owfs.conf) is
>
> server: link = /dev/ttyS0
> server: server = owserver.example.com:4304
> ---
>
> Seems like I've done that, and still get the slow response. Maybe if my
> original had been some DNS-requiring URI instead of "localhost", that timing
> would have been even worse?
>
>
> In Martin's reply:
> ---
>> In fact the original configuration (owfs.conf) is
>>
>> server: link = /dev/ttyS0
>> server: server = owserver.example.com <http://owserver.example.com>:4304
> ---
>
> I'm assuming that "http" link was added somewhere in the mailing list
> plumbing? But maybe both versions have been accidentally manipulated, and I'm
> not understanding the suggestion.
>
> (I suppose my post may be further manipulated, who knows what will be
> received from this. Guess there is no universal "pre" or "code" tag that
> would get tricky bits through the whole list pathway unchanged...)
>
>
>> The reason for this slow ?dir? seems linked in my case to a ?bug' in
>> owserver (debian version 2.8p15-1).
>
> I do have that very version:
> ubuntu@arm:~$ dpkg --list | grep owfs
> ii owfs 2.8p15-1ubuntu4 all Dallas 1-wire support
> ii owfs-common 2.8p15-1ubuntu4 all common files used by any of the
> OWFS programs
> ii owfs-doc 2.8p15-1ubuntu4 all Dallas 1-wire support:
> Documentation for owfs
> ii owfs-fuse 2.8p15-1ubuntu4 armhf 1-Wire filesystem
>
> And all my timings match your slow ones so well... Maybe I really haven't
> grasped where I need to put the numeric IP?
>
> | Loren Amelang | lo...@pacific.net |
>
>
>
>
> ------------------------------------------------------------------------------
> Presto, an open source distributed SQL query engine for big data, initially
> developed by Facebook, enables you to easily query your data on Hadoop in a
> more interactive manner. Teradata is also now providing full enterprise
> support for Presto. Download a free open source copy now.
> http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
------------------------------------------------------------------------------
Presto, an open source distributed SQL query engine for big data, initially
developed by Facebook, enables you to easily query your data on Hadoop in a
more interactive manner. Teradata is also now providing full enterprise
support for Presto. Download a free open source copy now.
http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
