This is from 2.7p19, so I apologize if it's been fixed since then... This involves two owserver instances, one of which is referencing and aggregating the other. So, two boxes. The host "slug" is running "owserver -p 4304 --fake=10,26,28" plus some debugging options. The host "troll" is running "owserver -p 4304 -u -s slug:4304". Both come up fine. To start with, running "owdir" on troll lists the real devices on its real 1-wire bus plus the 3 fake devices on slug, just as expected. Running "owdir bus.0" shows just the local stuff. Running "owdir bus.1" causes a seg fault on slug. The last debug message (at level 4) before the fault is "CALL: PARSENAME path=[bus.1]". If instead I run "owdir /bus.1", the owserver on slug doesn't crash, and everything goes as expected. The matching debug line shown on slug is "CALL: PARSENAME path=[]" in this case.
So, I can kind of see what's not going right, and it seems to be on the server (troll) end. Is there any additional information I can provide that would be of help? Has it already been fixed, perhaps, and I should just upgrade? Thanks, Rob ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
