在1.2.12版本 获取锁仍然还是存在bug about zlog HOT 3 OPEN

您说的地方改过了，还是2千多次锁在这：
#0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1 0x00007f7d2580ba24 in pthread_rwlock_rdlock () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_rwlock_rdlock.S:122
#2 0x00007f7d25c12047 in zlog (category=0x11b0cd0, file=0x401b73 "taskc.c", filelen=7, func=0x401c7a <FUNCTION.4360> "do_sig_child", funclen=12, line=189, level=30, format=0x401b80 "do_sig_child, pid=%d, tid=%d,sigs=%d\n") at zlog.c:1010
#3 0x00000000004013c6 in do_sig_child ()
#4
#5 pthread_rwlock_rdlock () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_rwlock_rdlock.S:47
#6 0x00007f7d25c12047 in zlog (category=0x11b0cd0, file=0x401b73 "taskc.c", filelen=7, func=0x401c87 <FUNCTION.4386> "main", funclen=4, line=323, level=30, format=0x401c39 "Parent ID %d\n") at zlog.c:1010
#7 0x0000000000401855 in main ()

from zlog.

他那个文件锁是日志配置文件锁
不是日志本身的文件锁
@zhouyuyu888
目前我已经在商用环境使用
没有出现问题

from zlog.

@enddeadroyal,zlog在一般场景中已经是非常安全了，我专门写的每秒并发50压力测试程序，的确都压出问题了，而且昨天试了一下，不轮转也有问题，日志文件写到58M就死锁了。

from zlog.