owfs
should allow complete concurrency, especially since it only sees the filesystem
calls and doesn't know there are multiple clients.
However, I'm a little confused by the "python bindings" If I understand
you correctly, you have owfs and owpython running at the same time. Can't do
that like that!!!
(Both
are talking to the adapter directly and don't know about the
other.)
The
correct way is to use owserver:
Example
owserver /dev/ttyS0 -p 3333
owfs
-s 3333 /mnt/1wire
owpython init(3333) (or whatever the owpython syntax is. In owperl it
would be OW::init(3333) )
The
point is that owserver handles the concurrency.
Paul
-----Original Message-----Hi: I'm new to owfs. I've d/l and built the latest owfs from cvs and have it up and running. It works well with a single client but I have problems with multiple clients and owf:
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Les Smithson
Sent: Monday, November 07, 2005 6:43 AM
To: owfs-developers@lists.sourceforge.net
Subject: [Owfs-developers] owfs concurrency
The 2nd client can't see any of my /mnt/1wire/10.* devices, and it also stops the 1st client from seeing them. Killing off both clients and restarting one allows the 1st client to see the devices again, eventually. If it makes any difference, I'm reading uncached using the Python bindings.
What are the concurrency issues with owfs? Does it serialise access? What about cached reads?
TIA.
--
Les Smithson <[EMAIL PROTECTED]>
Open Network Solutions Ltd
