Commit 8279d21d authored by Jeremy C. Reed's avatar Jeremy C. Reed
Browse files

This is for trac226.

Fix run_*.sh scripts that are used for development testing
so they use a msgq socket file in the build tree.

I didn't merge from that branch since had 21 conflicts and missing
ranges. My original commit message for r3881 was:

Set BIND10_MSGQ_SOCKET_FILE in environment for every run_*.sh
script (not for unittests though).
It is set to @abs_top_builddir@/msgq_socket

I didn't test all of them and some do not even use it. But it
shouldn't hurt.

This is for Trac ticket #226.

Note I don't patch the src/bin/recurse/run_b10-recurse.sh.in now.
It is now missing and I don't know why.



git-svn-id: svn://bind10.isc.org/svn/bind10/trunk@3989 e5f2f494-b856-4b98-b285-d166d9295462
parent 88316252
136. [bug] jreed
Fix run_*.sh scripts that are used for development testing
so they use a msgq socket file in the build tree.
(Trac #226, svn NNNN)
135. [bug] jelte
bindctl (and the configuration manager in general) now no longer
accepts 'unknown' data; i.e. data for modules that it does not know
......
......@@ -26,5 +26,8 @@ export PYTHONPATH
B10_FROM_SOURCE=@abs_top_srcdir@
export B10_FROM_SOURCE
BIND10_MSGQ_SOCKET_FILE=@abs_top_builddir@/msgq_socket
export BIND10_MSGQ_SOCKET_FILE
cd ${BINDCTL_PATH}
exec ${PYTHON_EXEC} -O bindctl $*
......@@ -22,6 +22,9 @@ CMD_CTRLD_PATH=@abs_top_builddir@/src/bin/cmdctl
PYTHONPATH=@abs_top_srcdir@/src/lib/python
export PYTHONPATH
BIND10_MSGQ_SOCKET_FILE=@abs_top_builddir@/msgq_socket
export BIND10_MSGQ_SOCKET_FILE
cd ${CMD_CTRLD_PATH}
${PYTHON_EXEC} b10-cmdctl
......@@ -21,5 +21,8 @@ export PYTHON_EXEC
PYTHONPATH=@abs_top_builddir@/src/lib/python
export PYTHONPATH
BIND10_MSGQ_SOCKET_FILE=@abs_top_builddir@/msgq_socket
export BIND10_MSGQ_SOCKET_FILE
LOADZONE_PATH=@abs_top_builddir@/src/bin/loadzone
exec ${LOADZONE_PATH}/b10-loadzone $*
......@@ -23,5 +23,8 @@ MYPATH_PATH=@abs_top_builddir@/src/bin/msgq
PYTHONPATH=@abs_top_srcdir@/src/lib/python
export PYTHONPATH
BIND10_MSGQ_SOCKET_FILE=@abs_top_builddir@/msgq_socket
export BIND10_MSGQ_SOCKET_FILE
cd ${MYPATH_PATH}
exec ${PYTHON_EXEC} -O b10-msgq $*
......@@ -21,6 +21,9 @@ export PYTHON_EXEC
PYTHONPATH=@abs_top_builddir@/src/lib/python
export PYTHONPATH
BIND10_MSGQ_SOCKET_FILE=@abs_top_builddir@/msgq_socket
export BIND10_MSGQ_SOCKET_FILE
B10_FROM_BUILD=@abs_top_builddir@
export B10_FROM_BUILD
......
......@@ -24,6 +24,9 @@ export PYTHONPATH
B10_FROM_BUILD=@abs_top_srcdir@
export B10_FROM_BUILD
BIND10_MSGQ_SOCKET_FILE=@abs_top_builddir@/msgq_socket
export BIND10_MSGQ_SOCKET_FILE
STATS_PATH=@abs_top_builddir@/src/bin/stats
cd ${STATS_PATH}
......
......@@ -20,6 +20,9 @@ export PYTHON_EXEC
MYPATH_PATH=@abs_top_builddir@/src/bin/usermgr
BIND10_MSGQ_SOCKET_FILE=@abs_top_builddir@/msgq_socket
export BIND10_MSGQ_SOCKET_FILE
cd ${MYPATH_PATH}
${PYTHON_EXEC} b10-cmdctl-usermgr
......@@ -22,6 +22,9 @@ MYPATH_PATH=@abs_top_builddir@/src/bin/xfrin
PYTHONPATH=@abs_top_srcdir@/src/lib/python:@abs_top_builddir@/src/lib/dns/.libs
export PYTHONPATH
BIND10_MSGQ_SOCKET_FILE=@abs_top_builddir@/msgq_socket
export BIND10_MSGQ_SOCKET_FILE
cd ${MYPATH_PATH}
${PYTHON_EXEC} b10-xfrin
......@@ -22,6 +22,9 @@ MYPATH_PATH=@abs_top_builddir@/src/bin/xfrout
PYTHONPATH=@abs_top_srcdir@/src/lib/python:@abs_top_builddir@/src/lib/xfr/.libs:@abs_top_builddir@/src/lib/dns/python/.libs
export PYTHONPATH
BIND10_MSGQ_SOCKET_FILE=@abs_top_builddir@/msgq_socket
export BIND10_MSGQ_SOCKET_FILE
cd ${MYPATH_PATH}
${PYTHON_EXEC} b10-xfrout
......@@ -22,6 +22,9 @@ MYPATH_PATH=@abs_top_builddir@/src/bin/zonemgr
PYTHONPATH=@abs_top_srcdir@/src/lib/python:@abs_top_builddir@/src/lib/dns/.libs
export PYTHONPATH
BIND10_MSGQ_SOCKET_FILE=@abs_top_builddir@/msgq_socket
export BIND10_MSGQ_SOCKET_FILE
cd ${MYPATH_PATH}
${PYTHON_EXEC} b10-zonemgr
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment