Issue 361 in roster-dns-management: Conncurrent DnsCheckConfig execution

0 views
Skip to first unread message

roster-dns...@googlecode.com

unread,
Feb 5, 2013, 11:28:43 AM2/5/13
to roster-iss...@googlegroups.com
Status: Accepted
Owner: dchaye...@gmail.com
Labels: Type-Defect Priority-Medium

New issue 361 by dchaye...@gmail.com: Conncurrent DnsCheckConfig execution
http://code.google.com/p/roster-dns-management/issues/detail?id=361

DnsCheckConfig should be run concurrently (locally) for each DNS server.
Start with a thread pool of 20.

roster-dns...@googlecode.com

unread,
Feb 8, 2013, 9:44:45 PM2/8/13
to roster-iss...@googlegroups.com

Comment #1 on issue 361 by J.S.P...@gmail.com: Conncurrent
DnsCheckConfig execution
http://code.google.com/p/roster-dns-management/issues/detail?id=361

Also, while you're at it, you should clean up dnscheckconfig. Right now it
has a lot of code that is essentially a copy of code in config_lib.py

roster-dns...@googlecode.com

unread,
Jul 12, 2013, 3:58:01 PM7/12/13
to roster-iss...@googlegroups.com
Updates:
Status: Fixed

Comment #2 on issue 361 by dchaye...@gmail.com: Conncurrent DnsCheckConfig
execution
http://code.google.com/p/roster-dns-management/issues/detail?id=361

Fixed in r1149.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Reply all
Reply to author
Forward
0 new messages