If you start owfs with the following commands as you said: owserver -u1 -u2 -t1 --foreground owhttpd -p 3002 -s 3001 --foreground
The directory structure should look like this: / (Directory with /system /settings /statistics etc.) /system/adapter/name.ALL = "tcp" /81.0000000000 (Devices on all adapters listed in root) /81.0000000001 /bus.0/ (Directory with /system /settings /statistics etc.) /bus.0/system/adapter/name.ALL = "DS9490,DS9490" /bus.0/81.0000000000 /bus.0/81.0000000001 /bus.0/bus.0/ (only devices from first USB-adapter) /bus.0/bus.0/81.0000000000 /bus.0/bus.1/ (only devices from second USB-adapter) /bus.0/bus.1/81.0000000001 It seems to be some bug if the directory /bus.0/bus.1 is empty for you. Try to read the directory "/uncached/bus.0/bus.1/" too just in case it could return your devices on the second usb-adapter. I don't have two USB-adpaters at home, so I can't really try it myself. Can somebody else verify if it's a bug for all users with multiple usb-adapters? /Christian On Wed, 2005-04-06 at 18:25 +0200, Sebastian Zuther wrote: > i am using: > "owserver -u1 -u2 -t1 --foreground" > > running "owserver -u -t1 --foreground" gives only access to the first usb > device. > > normally i am using the owphp extension, so owserver is all i am running. > i am not getting things like "connection refused". all i get is: no > bus.XX directories in the root directory, and when i do a get(/bus.1/) i > get an empty string. > > when using owhttpd (for debugging purposes) i run it as following: > "owhttpd -p 3002 -s 3001 --foreground" > > no error messages. just /bus.0/ is in the root directory, the bus.1 is in > the /bus.0/ subdirectory. when i am reading the /bus.1/ directory i am > getting: > "bus.1 > > top > highest level > directory > " > in owhttpd, which is an empty directory. > > i hope this helps a little bit, > bye > > sebastian. > > > > > Can you tell me which processes you start? Start the binaries with > > --foreground, and you will eventually see major error such as > > "connection refused" etc. I think that's what happens for you. > > The question is where it tries to connect... Things like this > > works for me. > > > > owserver --foreground -u -d /dev/ttyS0 -p 3001 & > > owhttpd --foreground -s 3001 -p 8000 & > > owfs --foreground -s 3001 /mnt/1wire & > > > > It would be helpful to know how you start owserver, otherwise it's > > impossible to know were to search for the problem. > > > > /Christian > > > > > > On Wed, 2005-04-06 at 15:26 +0200, [EMAIL PROTECTED] wrote: > > > > > > > > > > > > > another thing is that the bus.x directories don't show up. when > > > i > > > check > > > > > for "/bus.0/" it shows me all of the directories (which should > > > be > > > under > > > > > "/" as well, including "/bus.0/bus.1/" but when i check for > > > "/bus.1/" > > > it > > > > > breaks my connection to owserver or, in owhttp, reports an > > > empty > > > > > directory. > > > > > > -- > > Christian Magnusson <[EMAIL PROTECTED]> > > > -- Christian Magnusson <[EMAIL PROTECTED]> ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
