Owserver and owfs seem to be rock-stable or me right now during high load
from multiple clients.
Linksys: owserver
Owfs
Temploggerd
Host1: owfs
Temploggerd
Readbutton (utility which poll LCD-buttons as quick as possible
And print text to the display once every second, time+
tempterature)
What I can notice is that it's much slower to print text to the LCD-display
now, and sometimes I can't print a text-row every second. This was not a
problem for me before.
[Utomhus: 1.00 ] to [/var/1wire//uncached/FF.710200000100/line16.1]
[19/02 23:17:41 ] to [/var/1wire//uncached/FF.710200000100/line16.1]
[19/02 23:17:43 ] to [/var/1wire//uncached/FF.710200000100/line16.1]
[Utomhus: 1.00 ] to [/var/1wire//uncached/FF.710200000100/line16.1]
[19/02 23:17:48 ] to [/var/1wire//uncached/FF.710200000100/line16.1]
[19/02 23:17:49 ] to [/var/1wire//uncached/FF.710200000100/line16.1]
[19/02 23:17:51 ] to [/var/1wire//uncached/FF.710200000100/line16.1]
[Utomhus: 0.94 ] to [/var/1wire//uncached/FF.710200000100/line16.1]
The most important thing is that it's stable now... Tuning with high load is
not that important I think, but it's worth looking at when you can notice
that too.
I haven't looked at the fuse-exit problem, but it might be some
signal-handler that tries to exit nicely + main-function tries to cleanup as
well.
/Christian
-----Ursprungligt meddelande-----
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] För Paul Alfille
Skickat: den 19 februari 2006 20:25
Till: [email protected]
Ämne: Re: SV: SV: [Owfs-developers] Timeout again
On Sunday 19 February 2006 02:07 pm, Christian Magnusson wrote:
>
> It seems to be very slow response-time now, but I'll tell you more about
my
> experience when it has been running for some more time.
Yes the response times seem a little slow. Strange, since I eliminated an
unneeded ServerPresence communication with every remote directory element.
There is also a dropped pointer when reading real devices with fuse
(glibc error -- actually doubly freed pointer) that you can seen in
--foreground mode.
fuse: fuse_remove_signal_handlers: unknown session
*** glibc detected *** free(): invalid pointer: 0x080694b0 ***
*** glibc detected *** free(): invalid pointer: 0x080673b0 ***
*** glibc detected *** free(): invalid pointer: 0x080694e8 ***
fuse: fuse_remove_signal_handlers: unknown session
*** glibc detected *** corrupted double-linked list: 0x401d27c8 ***
*** glibc detected *** corrupted double-linked list: 0x401d27c8 ***
The error occurs only in owfs, not owserver, or owhttpd. And the error
occurs
with both remote and local buses. It occurs with listing or reading actual
devices, but not statistics or other memory elements.
>
> I will probably need to do some more serious multitasking tomorrow
> afternoon since we will probably deliver our twins then. :)
>
I can understand if "nice" us a bit.
> /Christian
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
