I've tried to replicate the problem (starting owserver without full path to
device) and the program seems to behave appropriately. (simplified...)
paul@gateway:~/owfs$ sudo /opt/owfs/bin/owserver --debug -d ttyUSB0
0x1c0c010 alloc owserver.c:[52] STRDUP s=/opt/owfs/bin/owserver
DEBUG MODE
libow version:
2.8p15
DEBUG: ow_daemon.c:(167) main thread id = 139699029157632
DEBUG: ow_avahi_link.c:(75) Avahi support: libavahi-client loaded
successfully
....
DEBUG: ow_avahi_link.c:(109) Avahi library function found: avahi_strerror
CALL: ow_parsename.c:(98) path=[]
DEBUG: owlib.c:(82) Globals temp limits 0C 100C (for simulated adapters)
DEBUG: ow_ds9097U.c:(279) Attempt 0 of 3 to initialize the DS9097U
DEBUG: ow_net_client.c:(84) IP address=[ttyUSB0] port=[10001]
CONNECT: ow_net_client.c:(146) [Connection refused] Socket problem
DEBUG: ow_ds9097U.c:(279) Attempt 1 of 3 to initialize the DS9097U
CONNECT: ow_net_client.c:(146) [Connection refused] Socket problem
DEBUG: ow_ds9097U.c:(279) Attempt 2 of 3 to initialize the DS9097U
CONNECT: ow_net_client.c:(146) [Connection refused] Socket problem
DEBUG: ow_ds9097U.c:(264) Could not initilize the DS9097U even after
several tries
CONNECT: ow_net_client.c:(146) [Connection refused] Socket problem
CONNECT: owlib.c:(128) Cannot detect DS2480 or LINK interface on ttyUSB0.
Should we insist on an absolute path? Are there any cases where absolute
device path isn't needed?
Paul Alfille
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
