>> libdl.so.2 => /lib/libdl.so.2 (0x4001e000) >> libpthread.so.0 => /lib/i686/libpthread.so.0 (0x40022000) >> libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 >> (0x40037000) libm.so.6 => /lib/i686/libm.so.6 (0x40079000) >> libc.so.6 => /lib/i686/libc.so.6 (0x4009c000) >> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) > > Hmm, are you sure this is a glibc 2.2.x setup? It seems a 2.3.x.
Yes, sure. A rpm -qa | grep glibc says that. > Note that this is not an XMail problem. The fact that a pretty large > number of XMail setups on Linux run fine and the fact that setting > LD_ASSUME_KERNEL=2.4 solved the issue in other machines, tells pretty > much that it is an underlying glibc/kernel thing. Did you try to do > an: > > export LD_ASSUME_KERNEL=2.4 > > in your XMail startup script? Did you notice any difference in the RSS > growing? It's now by 1844 after 1 Minute of uptime and growing very slowly or being persistent. After the first crash we had LD_ASSUME_KERNEL=2.4.1, not LD_ASSUME_KERNEL=2.4 - does it make any difference? Is it normal, that the LD_ASSUME_KERNEL does not appaer in "set" output after i executed the XMail startup script, but if i type export LD_ASSUME_KERNEL=2.4 in the shell, it is the the "set"-command. -- Soenke - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
