Am Dienstag, 3. Oktober 2006 03:07 schrieb Alfille, Paul H.,M.D.:
> B. Cache will fill with more devices. It is flushed automatically, and
> degrades gracefully when full. Currently full is triggered my memory
> allocation failure, but we could be more elegant if required. (Memory is
> part of the general pool, and memory allocation failure will upset other
> OWFS functions).
>
Hmmm...malloc() will *never* fail on standard linux distributions, apart from
exhausting the process address space -- 3GB on most i386 distributions.
(This may be changed with echo 2 >/proc/sys/vm/overcommit_memory by the system
administrator).
Instead, if virtual memory is exhausted, random processes get killed. It would
be a wise idea that owfs, as a long-running background process, had some
internal limit in its memory usage.
Kind regards
Jan
--
"I'm not a programmer, but I play one at Microsoft."
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
