On 11/06/2015 07:33 PM, Jan Kandziora wrote:
Am 06.11.2015 um 16:32 schrieb Martin Patzak (GMX):
Hello All,
owserver version 2.9p8 does not print information set by --error_level
and the use of --foreground or --debug
--debug implies --foreground and --error_level settings, so no need to
set these.
yes, true, --foreground is not necessary when using --debug.
With owfs I can use --debug and additionally an --error_level setting to
select the amount of debug information
--foreground I used to see if owserver need this
I doubt it. I your last mail, you posted only a minimal set of
information printed by the owfs binary. I think these aren't printed iut
by the --debug mechanism, so they are always there.
-------------------------------------------
here is the print out and proof from owfs right after starting it up:
also when I start owfs directly, without using owserver, debugging still
works for owfs
-------------------------------------------
mnm@razmaban:~/owfs/owfs_151104$ sudo owfs -s 4304 -m /mnt/1wire
--allow_other --debug --error_level=3
[sudo] password for mnm:
DEBUG MODE
libow version:
2.9p8
FUSE library version: 2.9.3
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.18
flags=0x0000047b
max_readahead=0x00020000
INIT: 7.19
flags=0x00000011
max_readahead=0x00020000
max_write=0x00020000
max_background=0
congestion_threshold=0
unique: 1, success, outsize: 40
a directory call looks like this:
unique: 2, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 1722
getattr /
unique: 2, success, outsize: 120
unique: 3, opcode: OPENDIR (27), nodeid: 1, insize: 48, pid: 1722
unique: 3, success, outsize: 32
unique: 4, opcode: READDIR (28), nodeid: 1, insize: 80, pid: 1722
getdir[0]
unique: 4, success, outsize: 2632
unique: 5, opcode: READDIR (28), nodeid: 1, insize: 80, pid: 1722
unique: 5, success, outsize: 16
unique: 6, opcode: RELEASEDIR (29), nodeid: 1, insize: 64, pid: 0
unique: 6, success, outsize: 16
reading the CRC16_error looks like:
unique: 15, opcode: LOOKUP (1), nodeid: 1, insize: 51, pid: 2123
LOOKUP /statistics
getattr /statistics
NODEID: 2
unique: 15, success, outsize: 144
unique: 16, opcode: LOOKUP (1), nodeid: 2, insize: 47, pid: 2123
LOOKUP /statistics/errors
getattr /statistics/errors
NODEID: 3
unique: 16, success, outsize: 144
unique: 17, opcode: LOOKUP (1), nodeid: 3, insize: 53, pid: 2123
LOOKUP /statistics/errors/CRC16_errors
getattr /statistics/errors/CRC16_errors
NODEID: 4
unique: 17, success, outsize: 144
unique: 18, opcode: OPEN (14), nodeid: 4, insize: 48, pid: 2123
open flags: 0x20000 /statistics/errors/CRC16_errors
open[0] flags: 0x20000 /statistics/errors/CRC16_errors
unique: 18, success, outsize: 32
unique: 19, opcode: READ (15), nodeid: 4, insize: 80, pid: 2123
read[0] 131072 bytes from 0 flags: 0x20000
read[0] 1 bytes from 0
unique: 19, success, outsize: 17
unique: 20, opcode: READ (15), nodeid: 4, insize: 80, pid: 2123
read[0] 131072 bytes from 1 flags: 0x20000
read[0] 0 bytes from 1
unique: 20, success, outsize: 16
unique: 21, opcode: RELEASE (18), nodeid: 4, insize: 64, pid: 0
release[0] flags: 0x20000
unique: 21, success, outsize: 16
which gives me the *wrong value*. Thats why I started debugging to see
what owserver is doing with it
*CRC16_erros* on *owserver* is *15*, while it remains *0* on *owfs*.
---------------------------------
starting owserver with the almost same parameters (that is --debug and
--error_level=3)
---------------------------------
mnm@razmaban:~/owfs/owfs_151104$ sudo owserver --link=/dev/1-wire-link
--debug --error_level=3
[sudo] password for mnm:
DEBUG MODE
libow version:
2.9p8
*and that's all she wrote!*
You are using a build without debugging support. Please take the owfs
sources and configure/compile for yourself.
can it be, that owserver has no debugging support, while owfs does?
And why does it print DEBUG MODE at all?
Kind regards
Jan
Thank you,
Martin
------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
