[Varnish] #119: Problem with named servers, if first named server has no user-set name

[Varnish]

#119: Problem with named servers, if first named server has no user-set name
----------------------+-----------------------------------------------------
 Reporter:  cecilihf  |       Owner:  phk        
     Type:  defect    |      Status:  new        
 Priority:  normal    |   Milestone:  Varnish 2.0
Component:  varnishd  |     Version:  trunk      
 Severity:  normal    |    Keywords:             
----------------------+-----------------------------------------------------
 The introduction of the possibility to name varnish instances introduced a
 problem that might need som modified behaviour of mgt_param.c. The problem
 is that if a user starts varnish without specifying a name, this instance
 gets hostname as name. If the user then starts a new varnish, with another
 name, the behaviour of mgt_param.c causes this varnish instance to first
 be named the hostname, same as the first varnish instance, before changing
 the name to the new name. This is a problem because this results in
 renaming of the first varnish instance's directory where it stores its
 temporary filenames. The problem might have to be solved by changing the
 behaviour of mgt_param.c, so that default values are only set if the user
 has not specified any other values.

-- 
Ticket URL: <http://varnish.projects.linpro.no/ticket/119>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator