Out of memory and inactive memory
Hi, I'm running Zope under FreeBSD 4. Zope keeps getting memory errors, i.e. malloc() fails. But top reports lots of inactive memory available. I'm new to BSD, but I did search around in archives and I think I learned that inactive memory is only kept around in case it is needed again and should be given to a process needing it. So why does Zope fail here? Douwe Osinga http://www.world66.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Out of memory and inactive memory
Douwe Osinga wrote: I'm running Zope under FreeBSD 4. Zope keeps getting memory errors, i.e. malloc() fails. But top reports lots of inactive memory available. I'm new to BSD, but I did search around in archives and I think I learned that inactive memory is only kept around in case it is needed again and should be given to a process needing it. So why does Zope fail here? Do you happen to have a per-process data size limit? What does ulimit -a or limit show? The former is for sh or bash, the latter for csh or tcsh. Uwe -- Uwe Doering | EscapeBox - Managed On-Demand UNIX Servers [EMAIL PROTECTED] | http://www.escapebox.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Out of memory and inactive memory
Do you happen to have a per-process data size limit? What does Hey, thanks, that could be it. It says datasize limit = 130 Mbyte sort of where the process stopped working. Is there a way to change this setting on a global scale? I.e. if I limit datasize unlimited, it seems that only works for the current session. Thanks again, Douwe Osinga http://douweosinga.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Out of memory and inactive memory
Douwe Osinga wrote: Do you happen to have a per-process data size limit? What does Hey, thanks, that could be it. It says datasize limit = 130 Mbyte sort of where the process stopped working. Is there a way to change this setting on a global scale? I.e. if I limit datasize unlimited, it seems that only works for the current session. Provided it doesn't get set explicitly by a 'ulimit' or 'limit' command in some shell start-up script the datasize limit could be set in '/etc/login.conf'. If you change anything in there don't forget to run 'cap_mkdb /etc/login.conf' in order to re-generate the corresponding database file. Uwe -- Uwe Doering | EscapeBox - Managed On-Demand UNIX Servers [EMAIL PROTECTED] | http://www.escapebox.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
