- 11 Mar, 2013 1 commit
-
-
Michal 'vorner' Vaner authored
They save only little bit of work to the CPU and are suspicious to casual reader, even when they should be safe in theory.
-
- 07 Mar, 2013 1 commit
-
-
Michal 'vorner' Vaner authored
It should be allowed by C++ standard (and the object be alive before the function is left), but this is just to be sure.
-
- 06 Mar, 2013 1 commit
-
-
Michal 'vorner' Vaner authored
-
- 22 Feb, 2013 3 commits
-
-
Michal 'vorner' Vaner authored
Add tests for the fact and fix it. Also, add log from the rpcCall itself, so it can be seen in logs.
-
Michal 'vorner' Vaner authored
To help debugging.
-
Michal 'vorner' Vaner authored
-
- 20 Feb, 2013 2 commits
-
-
Michal 'vorner' Vaner authored
-
Michal 'vorner' Vaner authored
They currently fail, as the method is empty. Provide at least an empty implementation, to make it compile.
-
- 18 Feb, 2013 3 commits
-
-
Michal 'vorner' Vaner authored
-
Mukund Sivaraman authored
-
Naoki Kambe authored
-
- 17 Feb, 2013 1 commit
-
-
JINMEI Tatuya authored
should be trivial, directly committing.
-
- 15 Feb, 2013 3 commits
-
-
Naoki Kambe authored
As well as ffd4a283, in the platform (FreeBSD8, amd64), the timer counters can be zero. However get_statistics() in counters.py didn't calculate an entire server's counts if they are zero. This change is added so that it calculates counters even though they are zero. An new unittest is added to check that. This change fixes the issue reported in #2741. For details about errors related to this change, see the following build farm reports. http://git.bind10.isc.org/~tester/builder/BIND10-cppcheck/20130214075001-FreeBSD8-amd64-GCC/logs/unittests.out http://git.bind10.isc.org/~tester/builder/BIND10-cppcheck/20130206173746-FreeBSD8-amd64-GCC/logs/unittests.out http://git.bind10.isc.org/~tester/builder/BIND10-cppcheck/20130211135501-FreeBSD8-amd64-GCC/logs/unittests.out
-
JINMEI Tatuya authored
-
Mark Andrews authored
-
- 14 Feb, 2013 7 commits
-
-
Jeremy C. Reed authored
Update copyright year for guide. Update copyright year for messages manual. Also remove the paragraph introducing bind10 from the messages manual (it was incomplete, so misleading). These were in the script) This is trivial, so no review.
-
Jeremy C. Reed authored
This TODO was handled a few minutes ago.
-
JINMEI Tatuya authored
-
Shane Kerr authored
-
Mukund Sivaraman authored
-
Mukund Sivaraman authored
Conflicts: src/lib/datasrc/memory/memory_messages.mes src/lib/datasrc/memory_datasrc.cc
-
Michal 'vorner' Vaner authored
-
- 13 Feb, 2013 18 commits
-
-
Jeremy C. Reed authored
(note this is not the rc version, just the version for master)
-
Jeremy C. Reed authored
-
Jeremy C. Reed authored
-
Jeremy C. Reed authored
use a # hash mark before the Trac number use two tabs before the committer username.
-
Mukund Sivaraman authored
-
JINMEI Tatuya authored
-
-
Jeremy C. Reed authored
This had a quick review via jabber. They were missing in some files that were longer than a few lines. Not real important, but to be consistent.
-
JINMEI Tatuya authored
-
Mukund Sivaraman authored
-
Jeremy C. Reed authored
used reorder_message_file.py
-
JINMEI Tatuya authored
-
Jeremy C. Reed authored
-
Jeremy C. Reed authored
Some rewording to be clear about difference of bind10 and b10-init. Remove some trailing whitespace. Say the resolver is experimental. Also introduce resolver. In manpages, improve various SEE ALSO. Fix a wrong man page reference. This was reviewed via jabber.
-
Michal 'vorner' Vaner authored
Provide a "message undeliverable" error by the msgq daemon in case the sender declares it expects an answer and there's no recipient to send it to. Conflicts: src/bin/bindctl/run_bindctl.sh.in src/bin/sysinfo/run_sysinfo.sh.in src/lib/python/isc/cc/Makefile.am src/lib/python/isc/cc/session.py
-
Shane Kerr authored
-
Michal 'vorner' Vaner authored
It was moved to other makefile by accident while it should have been moved.
-
Naoki Kambe authored
This is an ad-hoc workaround for the failures in stats tests. It's okayed to be committed on jabber. Note that this workaround should be removed after a fundamental fix for stats tests (#1668) is done. An investigation task for the fix will be worked on #2689. For the details of the failures, see #2666 and http://git.bind10.isc.org/~tester/builder//BIND10-valgrind/20130212205704-CentOS5-x86_64-GCC/logs/unittests.out
-