I wouldn't think so - it should be baked in to the traffic_ctl binary. Do you mean you are using the same binaries to run both instances? In that case, yes, traffic_ctl would need some indication of which .sock to open. Looks like the the call to TSInit is the magic place, with a first argument of the path to the socket. The current implementation passes nullptr which I presume means "use the built in string" but it should be easy to pass something else there.
Tuesday, March 28, 2017, 11:58:40 AM, you wrote: > so basically I need to tell traffic_ctl to write to socket file in 'my > directory' rather than default build time directory. Which routine does the > notification to traffic_manager ?
