Hi,
I haven't built any new slug-version since the cvs-version contained bugs
that made it impossible for me to use.
When Paul have fixed the simultaneous bug which showed up after the
persistent-feature, I will make a new build.
(I just wanted to keep a stable build in the repository)
/Christia
On 1/25/07, Paul Alfille <[EMAIL PROTECTED]> wrote:
> Peter, have you looked persistent tcp connections? The strategy is to set
> the persistent bit in the SG parameter of the message, and if it is returned
> set, keep the same file descriptor open for the next message. If the next
> message fails,
I'd exercise the persistent TCP option, but I need a new build for the NSLU2.
Real Life(tm) has not allowed for any owfs time in the last two weeks or so,
sorry about the lack of updates. I've got ownet python module templates for the
new read directory function and the persistent TCP connectio
Found the problem -- it was in swig.i uu unsed by owperl, pwpython and
owphp. Fixed in the CVS.
I'm working on some "simultaneous" bugs that Chrstian found, then we'll make
a new release.
Peter, have you looked persistent tcp connections? The strategy is to set
the persistent bit in the SG param
Is he running owpython or owphp? Email seems to indicate owphp but I'm
not entirely clear.
- Peter
On 1/25/07, Paul Alfille <[EMAIL PROTECTED]> wrote:
> I'm guessing it's the python interface, since owread and owhttpd seem happy.
>
> Perhaps we are reading the entire buffer, rather than "size" b
I'm guessing it's the python interface, since owread and owhttpd seem happy.
Perhaps we are reading the entire buffer, rather than "size" bytes.
Paul Alfille
On 1/24/07, Paul Alfille < [EMAIL PROTECTED]> wrote:
Clearly sounds broken. Now to figure where.
On 1/23/07, pappapop <[EMAIL PROTECTE
The second problem "owserver" alone causing a segfault I've seen and will
upload a fix today.
I'll look at error_print=3 but is isn't needed if you do --foreground, the
error output will go to the console automatically.
Paul Alfille
On 1/25/07, George M. Zouganelis <[EMAIL PROTECTED]> wrote:
Paul,
I was trying on cvs head:
I have no debug output on
# owserver --foreground --error_print 3 --error_level 9 -p 4304 -d /dev/ttyS0
shouldnt --error_print 3 show on stderr ?
additionaly, executing just as below (i know they have no sense), i get a
segmentation fault.
# owserver
# owserv
