Re: Problems with edit_line and edit_defaults=>empty

2011-02-23 Thread Adalbert Michelic
* On Wed, 23 Feb 2011 at 8:33 -0500, Daniel V. Klein wrote: > The promises look good, and AFAICT you should always get 2 lines, but I'd > suggest the following change for you: > > vars: > any:: > "dns" string => "192.168.1.20"; > machineX:: > "search" string => "domain2";

Re: Problems with edit_line and edit_defaults=>empty

2011-02-23 Thread Daniel V. Klein
The promises look good, and AFAICT you should always get 2 lines, but I'd suggest the following change for you: vars: any:: "dns" string => "192.168.1.20"; machineX:: "search" string => "domain2"; !machineX:: "search" string => "domain1"; This makes it clearer

Problems with edit_line and edit_defaults=>empty

2011-02-23 Thread Adalbert Michelic
I have a problem with some constellations of edit_line bundles together with edit_defaults=>empty. I have included the simpler bundle of the two creating problems below -- my expectation would be to get an /etc/resolv.conf with two lines -- all machines expect machineX should have domain1 as search