Martin v. Löwis wrote:
> Melissa Evans schrieb:
>
>>I've modified grappy.py,
>>http://www.stacken.kth.se/~mattiasa/projects/grappy/, a postfix policy
>>daemon for greylisting. to use LDAP as a backend instead of SQL (with
>>python-ldap.) The daemon runs fine when testing but when I put it under
>
You can set an environment variable MALLOC_CHECK_ to influence the
behaviour of glibc
0 -> no error message program continues
1 -> error message, program continues
2 -> no error message, kills program
3 -> error message, kills program
Since the message only occured with my two programs at exit tim
Hi Melissa,
I run into similar problems after compiling python-ldap 2.2.0 for
Python 2.5 on SuSE Linux 9.3
and running a small commandline application
*** glibc detected *** double free or corruption (out): 0x40180788 ***
I realy suspect the _ldap.so file. I have not found a solution yet, but
will
Melissa Evans schrieb:
> I've modified grappy.py,
> http://www.stacken.kth.se/~mattiasa/projects/grappy/, a postfix policy
> daemon for greylisting. to use LDAP as a backend instead of SQL (with
> python-ldap.) The daemon runs fine when testing but when I put it under
> load it core dumps quickly.
Hi. I'm new to Python. :)
I've modified grappy.py,
http://www.stacken.kth.se/~mattiasa/projects/grappy/, a postfix policy
daemon for greylisting. to use LDAP as a backend instead of SQL (with
python-ldap.) The daemon runs fine when testing but when I put it under
load it core dumps quickly.