On Thu, Sep 08, 2011 at 02:22:29PM +0200, Brane F. Gra??nar wrote: > On Thursday 08 of September 2011 11:21:34 Finn Arne Gangstad wrote: > > On Thu, Sep 08, 2011 at 07:43:46AM +0200, Willy Tarreau wrote: > > > Hi again, > > > > > > This morning I had an better idea : pass the "config directory" parameter > > > on the command line and have haproxy chdir() to it. That way, everything > > > specified after it is relative to this dir, and you don't need a full > > > path > > > > > > for config files. Eg : > > > haproxy -C /etc/haproxy -f haproxy.cfg > > > > > > I think it's easier to explain and to understand than previous proposal, > > > and it can completely solve your multi-machine issue (well doing "cd" > > > before starting haproxy also does, but I agree it can be less convenient, > > > especially when copy-pasting a command line from "ps"). > > What about settings this varible by itself, for example, setting it by > dirname(config_file) inside haproxy?
Because it's all but obvious for someone who doesn't know the product and has to manage it. And BTW, we have as many config files as we want, to that becomes impossible to sort out when they lie into different dirs. Regards, Willy
