Re: DBERROR: Cannot allocate memory
Thanks for this info. Probably should have done a search of the db3 docs, I just assumed it was a system thing. Duh. For anyone else experiencing this problem, the relevant docs are here: http://www.sleepycat.com/docs/api_c/env_set_cachesize.html The line you want to add to the DB_CONFIG file is: set_cachesize gigabytes bytes nallocations_to_breakinto The default size (which cyrus uses) is 256kb Rob - Original Message - From: "Lawrence Greenfield" <[EMAIL PROTECTED]> To: "Rob Mueller" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Friday, December 06, 2002 3:31 PM Subject: Re: DBERROR: Cannot allocate memory > --On Friday, December 06, 2002 1:09 PM +1100 Rob Mueller <[EMAIL PROTECTED]> > wrote: > > > This is probably more a berkeley DB question, but I'm wondering if anyone > > else has seen this. Every now and then we see this in our imap log. > > > > Dec 5 20:39:47 server2 lmtpd[24962]: DBERROR db3: Unable to allocate 4151 > > bytes from mpool shared region: Cannot allocate memory > > Dec 5 20:39:47 server2 lmtpd[24962]: DBERROR: mystore: error storing > > : Cannot allocate memory > [...] > > Anyway, has anyone else experienced this, or know of a solution? > > This probably means you need to increase the size of one of the db memory > pool, also known as the cache. It has nothing to do with system shared > memory: the db memory pool is an mmap()d file in the db/ directory. > > You can do this by making a DB_CONFIG file in the db/ directory that > contains... lemme see... if it contains "set_cachesize > " that should override what Cyrus compiles in with > the set_cachesize() function call. > > Larry > > >
Re: Buffer overflow in Cyrus IMAP ?
> I don't see why it existing with literals after login would concern you if > it didn't concern you before login. In our configuration we were more concerned about post login. We have done some more testing and it appears that this is a none issue in the 64 bit environment. Thanks for your comments. saira > > Of course, they are properly limited in 2.1.11 and 2.0.17. > > -Rob > > On Thu, 5 Dec 2002 [EMAIL PROTECTED] wrote: > > > Hi, > > > > Regarding the recently announced vulnerability > > > > http://online.securityfocus.com/archive/1/301864/2002-11-29/2002-12-05/0 > > > > Does a similar vulnerability exist with literals after login? > > > > Thank you. > > > > Saira Hasnain > > > > > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 > Research Systems Programmer * /usr/contributed Gatekeeper >
Re: Problems with ./configure on SunOS 9
--On Wednesday, December 08, 2027 11:13 PM +0100 [EMAIL PROTECTED] wrote: Laurent Larquère wrote: Thank you very much ! We´ve tried it this way now. And ... IT WORKS ! :) It´s been a long time now that i´ve had my hands on a non-linux system and so i relied 100% on the configure-script :/ I thought it is supposed to do things properly, you know :) The cyrus configure scripts still need some work. Does anyone know if they work with the current autoconf yet? I've been waiting for that to happen before I go in and fix the pathing problems, as I really am not set up to test autoconf 2.13. -- Carson
Re: Problems with ./configure on SunOS 9
Laurent Larquère wrote: > > [EMAIL PROTECTED] wrote: > > >Hi !!! > > > >After many tries and tracing the inner workings of the > >configure-script we ran into a grinding halt with cyrus-imapd 2.1.11 > >The configure-script complains about not being able to find > >"libsasl2" ... ( or sasl.h ? ). > >But the cyrus-sasl package 2.1.9 IS installed and we have (of > >course :) ) used the option "--with-sasl=PATH-TO-SASL-INSTALLATION" > >It seems to be a problem with the autoconf-script. > > > >The question is : has anyone compiled cyrus-imapd-2.1.11 with > >cyrus-sasl-2.1.9 using gcc and gnu-make on SunOS 9 ??? > > > >thank you in advance > >[EMAIL PROTECTED] > > > > > Yes, i have > and it runs like a charm > > i use CFLAGS="..." CPPFLAGS="..." LDFLAGS="..." LIBS="..." ./configure > --prefix=... > to give -I and -L of sasl2 to the configure script Thank you very much ! We´ve tried it this way now. And ... IT WORKS ! :) It´s been a long time now that i´ve had my hands on a non-linux system and so i relied 100% on the configure-script :/ I thought it is supposed to do things properly, you know :) Greetings from germany [EMAIL PROTECTED]
Re: Problems with ./configure on SunOS 9
[EMAIL PROTECTED] wrote: Hi !!! After many tries and tracing the inner workings of the configure-script we ran into a grinding halt with cyrus-imapd 2.1.11 The configure-script complains about not being able to find "libsasl2" ... ( or sasl.h ? ). But the cyrus-sasl package 2.1.9 IS installed and we have (of course :) ) used the option "--with-sasl=PATH-TO-SASL-INSTALLATION" It seems to be a problem with the autoconf-script. The question is : has anyone compiled cyrus-imapd-2.1.11 with cyrus-sasl-2.1.9 using gcc and gnu-make on SunOS 9 ??? thank you in advance [EMAIL PROTECTED] Yes, i have and it runs like a charm i use CFLAGS="..." CPPFLAGS="..." LDFLAGS="..." LIBS="..." ./configure --prefix=... to give -I and -L of sasl2 to the configure script smime.p7s Description: S/MIME Cryptographic Signature
Problems with ./configure on SunOS 9
Hi !!! After many tries and tracing the inner workings of the configure-script we ran into a grinding halt with cyrus-imapd 2.1.11 The configure-script complains about not being able to find "libsasl2" ... ( or sasl.h ? ). But the cyrus-sasl package 2.1.9 IS installed and we have (of course :) ) used the option "--with-sasl=PATH-TO-SASL-INSTALLATION" It seems to be a problem with the autoconf-script. The question is : has anyone compiled cyrus-imapd-2.1.11 with cyrus-sasl-2.1.9 using gcc and gnu-make on SunOS 9 ??? thank you in advance [EMAIL PROTECTED]
