Hi Patrik,
Thanks for finding this problem. It's been fixed and will be part of
the next release.
Basically you found 2 problems:
1. We need to handle structure/1F/aux as a file, and
1F.123412341234/aux as a directory.
2. We were too lenient with filenames.
10.12341234/id # is a file
10.12341234/id/foo # is not a file, but was being allowed and
treated like 10.12341234/id
So now:
$ owread /structure/1F/aux
D,000000,000001,oo,000008,v,
$ owread /structure/1F/aux/foo
ServerRead: Data error on /structure/1F/aux/foo
Paul Alfille
2011/6/20 Patrik Åkerfeldt <patrik.akerfe...@gmail.com>:
> I'm still having difficulties with structure.
> For example, I would expect /opt/owfs/bin/owread -s 192.168.1.10:3001
> /structure/1F/main to return proper response saying this is a directory
> instead of: ServerRead: Data error on /structure/1F/main
> And I would expect /opt/owfs/bin/owpresent -s 192.168.1.10:3001
> /structure/10/id/foobar to return 0 (instead of 1).
> Can I add these to the feature request list? :)
> Or is there a rationale to why this is so?
> Cheers,
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
