Are you running 2 different versions on the same machine? The libraries will conflict if you are. In fact, the library will stay in memory until all the programs using it are closed.
Otherwise, I don't have an obvious culprit. While BSD wasn't tested specifically, there weren't recent changes that should have caused problems. "Should" is an error-prone statement though. Paul On Wed, Apr 2, 2014 at 1:42 AM, Johan Ström <jo...@stromnet.se> wrote: > Hi, > > I'm testing the 2.9p3 release on FreeBSD 8.4. I'm currently running > 2.9p1 without problems, but with p3 it seems the owserver want's to exit > as soon as it has served a single request? > > Running my main owserver (2.9p1) on port 4304, starting the p3 server on > 4305: > > $ export LD_LIBRARY_PATH=/usr/ports/comms/owfs/work/stage/usr/local/lib > $ /usr/ports/comms/owfs/work/stage/usr/local/bin/owserver --debug > --foreground -s localhost:4304 -p 4305 > DEBUG MODE > libow version: > 2.9p3 > DEBUG: ow_daemon.c:(166) main thread id = 34374435264 > CALL: ow_parsename.c:(99) path=[] > DEBUG: owlib.c:(81) Globals temp limits 0C 100C (for simulated adapters) > DEBUG: ow_net_client.c:(85) IP address=[localhost] port=[4304] > CONNECT: ow_zero.c:(145) Zeroconf and/or Multithreading are not enabled > > (executing owdir -s localhost:4305 /system ) > > DEBUG: ow_tcp_read.c:(64) attempt 24 bytes Time: 10.000000 seconds > DEBUG: ow_tcp_read.c:(114) read: 24 - 0 = 24 > DEBUG: from_client.c:(67) FromClient payload=8 size=0 type=7 sg=0x10A > offset=0 > DEBUG: from_client.c:(75) FromClient (no servermessage) payload=8 > size=0 type=7 controlflags=0x10A offset=0 > DEBUG: ow_tcp_read.c:(64) attempt 8 bytes Time: 10.000000 seconds > DEBUG: ow_tcp_read.c:(114) read: 8 - 0 = 8 > DEBUG: handler.c:(153) START handler /system > CALL: data.c:(104) DataHandler: parse path=/system > DEBUG: ow_parseobject.c:(164) /system > CALL: ow_parsename.c:(99) path=[/system] > CALL: data.c:(164) Directory message (all at once) > DEBUG: dirall.c:(66) OWSERVER Dir-All SpecifiedBus=0 path = /system > DEBUG: ow_dir.c:(76) path=/system > CALL: ow_dir.c:(100) path=/system > DEBUG: ow_dir.c:(796) called on /system > CALL: ow_parsename.c:(99) path=[/system/configuration] > DEBUG: ow_parsename.c:(62) /system/configuration > CALL: ow_parsename.c:(99) path=[/system/connections] > DEBUG: ow_parsename.c:(62) /system/connections > CALL: ow_parsename.c:(99) path=[/system/process] > DEBUG: ow_parsename.c:(62) /system/process > DEBUG: ow_dir.c:(195) ret=0 > DEBUG: ow_parsename.c:(62) /system > DEBUG: data.c:(194) DataHandler: FS_ParsedName_destroy done > DEBUG: data.c:(208) DataHandler: cm.ret=0 > DEBUG: to_client.c:(67) payload=58 size=57, ret=0, sg=0x10A offset=0 > DEBUG: data.c:(227) Finished with client request > DEBUG: handler.c:(135) OWSERVER handler done > $ echo $? > 1 > $ > > The same thing happens if I do a owdir on / (it does properly list all > my nodes). > Using the p1 binary, the above works as expected (i.e. not exiting). > I have not tested p2. I have no extra patches. > > Any ideas? > > Best regards > Johan > > > ------------------------------------------------------------------------------ > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers >
------------------------------------------------------------------------------
_______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
