Commit d3442672 authored by Poul-Henning Kamp's avatar Poul-Henning Kamp

Use the nice macros we have, to make even this test use randomly

selected port numbers.

I belive varnishtest is now entirely without magic TCP port numbers
and multiple instances should be runable without collision.



git-svn-id: http://www.varnish-cache.org/svn/trunk/varnish-cache@4489 d4fa192b-c00b-0410-8231-f00ffab90ce4
parent 6a54c16c
...@@ -24,15 +24,12 @@ varnish v1 -vcl+backend { ...@@ -24,15 +24,12 @@ varnish v1 -vcl+backend {
varnish v1 -cliok "param.set diag_bitmap 0x00001000" varnish v1 -cliok "param.set diag_bitmap 0x00001000"
# We have to force a known listen address otherwise the client cannot find # Force the (random) port selected to be used again after restart.
# the varnish after the restart. varnish v1 -cliok "param.set listen_address ${v1_sock}"
varnish v1 -cliok "param.set listen_address 127.0.0.1:9080" -stop -start
# varnishtest defaults to auto_restart off, to avoid masking bugs. # varnishtest defaults to auto_restart off, to avoid masking bugs.
varnish v1 -cliok "param.set auto_restart on" varnish v1 -cliok "param.set auto_restart on"
client c1 { client c1 {
txreq -url "/" txreq -url "/"
rxresp rxresp
......
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