Displaying 2 results from an estimated 2 matches for "lock_info".
2005 Aug 25
2
Something other than dotlock for uidlist locking?
If I read the code correctly, only dotlocks are supported for locking
of dovecot-uidlist. And I don't see any settings in the config file
for it.
As it turns out, dotlocks are very slow on my system, due to their
implementation via hardlinks.
Would it be possible to support other locking mechanisms for locking
of the uidlist file?
-jdb
2007 Oct 31
1
segfault - asterisk crash and restart
...= (void *) 0x41373940
not_first_call = 0
ret = (void *) 0x37e8344898
a = {start_routine = 0x2aaab117330d <mixmonitor_thread>,
data = 0x1bb08220,
name = 0x1b892880 "mixmonitor_thread started at [ 301]
app_mixmonitor.c launch_monitor_thread()"}
lock_info = (struct thr_lock_info *) 0x1ba87c20
#5 0x00000037e8c061b5 in start_thread () from /lib64/libpthread.so.0
No symbol table info available.
#6 0x00000037e80cd36d in clone () from /lib64/libc.so.6
No symbol table info available.
#7 0x0000000000000000 in ?? ()
No symbol table info available.
(gdb)...