On Wed, 24 Aug 2005, Davide Libenzi wrote: > On Wed, 24 Aug 2005, CLEMENT Francis wrote: > >> To try to eliminate the problem, I deleted it (glst.dbm) (after saving = >> old >> in case ...) >> Glst created a new fresh >> Then after doing that, no more glst process staying active and taking = >> up to >> 99 cpu ! >> So, IMHO, this is a gdbm (win32 version only ?) problem when mlany = >> multi >> processes access the data base and the database becomes too big ... = >> (delays >> in accessing keys indexes ? not enough retries ? ...) >> Hope this can help you. > > Yes. I looked at the Win32 port, and the locking of the GDBM file is > incorrectly done with LockFile() (that does not block). I might try to make a > better Win32 port ASAP.
Could ppl having problem with CPU utilization of GLST with those Win32 binaries a shot? http://www.xmailserver.org/glst-newbin.zip - Davide - 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]
