BIND 10 #283: Xfrout uses different socket file than b10-auth when ran from source
BIND 10 Development
do-not-reply at isc.org
Tue Aug 10 01:37:45 UTC 2010
#283: Xfrout uses different socket file than b10-auth when ran from source
-------------------------+--------------------------------------------------
Reporter: jreed | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: xfrout | Resolution:
Keywords: | Sensitive: 0
Estimatedhours: 0.0 | Hours:
Billable: 0 | Totalhours:
Internal: 0 |
-------------------------+--------------------------------------------------
Comment(by zhanglikun):
Replying to [comment:2 jreed]:
> I still have the problem. I don't see in auth where it is set. As I only
see hardcoded: XfroutClient xfrout_client(UNIX_SOCKET_FILE);
What's the problem? is it mean the problem
{{{
"When running run_bind.sh in source tree, the socket file is at
./auth_xfrout_conn in the source, but Xfrout wants to use a non-existing
file located in the installation prefix:
"
}}}
BTW, the socket file wasn't designed as changeable, since it's the
communication agreement between auth and xfrout.
> Also the error I get is:
> [b10-auth] Error in handling XFR request: socket connect failed:
Connection refused
>
> (and an AXFR request results in SERVFAIL.)
This is one bug, and it has been catched by ticket #299(see more detail
information in that ticket), will fix soon.
--
Ticket URL: <https://bind10.isc.org/ticket/283#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list