bind dlz(mysql)运行过程时出现如下错误:
dlz "Mysql zone" { database "mysql {host=localhost dbname=mydns_data ssl=false port=3306 user=root pass=sok12345} {select zone from dns_records where zone = '%zone%'} {select ttl, type, mx_priority, case when lower(type)='txt' then concat('\"', data, '\"') else data end from dns_records where zone = '%zone%' and host = '%record%' and not (type = 'SOA' or type = 'NS')} {select ttl, type, mx_priority, data, resp_person, serial, refresh, retry, expire, minimum from dns_records where zone = '%zone%' and (type = 'SOA' or type='NS')} {select ttl, type, host, mx_priority, data, resp_person, serial, refresh, retry, expire, minimum from dns_records where zone = '%zone%' and not (type = 'SOA' or type = 'NS')}";# {select zone from xfr_table where zone = '%zone%' and client = '%client%'}# {update data_count set count = count + 1 where zone ='%zone%'}";};将配置节dlz "Mysql zone"中的%号更改为$符号即可。
“Some versions of DLZ used '%' to demarcate tokens, but they can cause problems for the LDAP driver. Subsequent patches have changed the token demarcation to '$'. It looks like your updated version (that's failing) is using the '$' symbols. If your config file is a few years old and still using the '%', it will suddenly fail at startup.
Simple solution is to check what your file is using around the tokens, and if it's '%', change them to '$' after the upgrade.”
而且直接配置文件是效率最高的,通过其它驱动效率都相对较低,BDB
这个测试不太准确,看官方的测试结果:http://bind-dlz.sourceforg
为什么使用BDB时QPS这么低? 我在bind版本基本相似的环境中测试的
It is quite useful and interesting too.
VIRT 的上限是64G,也就是36位, cat /proc/cpuinfo的结果是:addre
昨天要准备用线程重写webbench,试验了下Fedora Linux 2.6.35.14
不明白您的具体的意思是什么?
已经发送到你QQ邮箱