Am 13.06.2013 10:27, schrieb Mick Sulley:
> OK here is the log, hope that helps, I confess it doesn't mean much to
> me:) This is just the end section when the error occurred, if you need
> more please let me know.
> Mick
>
> NODEID: 2
> unique: 370, success, outsize: 144
> unique: 371, opcode: LOOKUP (1), nodeid: 2, insize: 52, pid: 5196
> LOOKUP /10.0D54A9010800/temperature
> getattr /10.0D54A9010800/temperature
> CALL: ow_fstat.c:(22) path=/10.0D54A9010800/temperature
> CALL: ow_parsename.c:(98) path=[/10.0D54A9010800/temperature]
> DEBUG: ow_cache.c:(926) Looking for device 10 0D 54 A9 01 08 00 DC
> DEBUG: ow_cache.c:(1082) Search in cache sn 10 0D 54 A9 01 08 00 DC
> pointer=0x7f7db098842c index=0 size=4
> DEBUG: ow_cache.c:(1098) Value found in cache. Remaining life: 24
> seconds.
> DEBUG: ow_presence.c:(76) Found device on bus 0
> CALL: ow_fstat.c:(39) ATTRIBUTES path=/10.0D54A9010800/temperature
> DEBUG: ow_parsename.c:(62) /10.0D54A9010800/temperature
> NODEID: 132
> unique: 371, success, outsize: 144
>
>
ow_dir isn't mentioned so this isn't the log section which returns
ENOTDIR. I guess there's a similar section a couple of lines above,
where Nautilus makes an unsucessful attempt - which causes the error.
Kind regards
Jan
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
