Hi, Yes, that is. I fixed this issue and updated 4.49 distribution tarball on http://www.dataparksearch.org/
Thank you. --- In [email protected], Sander Pool <[EMAIL PROTECTED]> wrote: > > > Hi, > > mutex.c has a hardcoded #define LOCK_DEBUG (or was it DEBUG_LOCK? going > from memory here). Curious that no one reported that during testing. Oh > well, easy fix. > > Sander > > Sander Pool wrote: > > > > > > Hi, > > > > 4.49 is bit too chatty for its own good. It always chats about locks and > > unlocks: > > > > [12059]{00} 0 Try lock db.c 704 > > [12059]{00} 0 locked db.c 704 > > [12059]{00} 0 Try unlock db.c 715 > > [12059]{00} 0 unlocked db.c 715 > > [12059]{00} 3 Try lock db.c 779 > > [12059]{00} 3 locked db.c 779 > > [12059]{00} 3 Try unlock db.c 796 > > [12059]{00} 3 unlocked db.c 796 > > [12059]{00} 0 Try lock cache.c 2386 > > [12059]{00} 0 locked cache.c 2386 > > > > I'll revert to 4.48 for now. My cronjob needs to be silent unless > > something drastic happens. > > > > Thanks, > > > > Sander > > > > >
