[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Other possible cfengine weak areas?
From: |
Wheeler, John |
Subject: |
RE: Other possible cfengine weak areas? |
Date: |
Thu, 22 Jan 2004 10:42:43 -0600 |
> On 22 Jan, Jamie Wilkinson wrote:
> > This one time, at band camp, Systems Administrator wrote:
> >>- Network interface setup. I wanted to be able to set up multiple
> >> virtual network interfaces with different IPs, based on the
> >> primary IP. I integrated this into the Package Management
> >> software above, since it already had a hosts table, and just
> >> needed an Interfaces table
> >
> > I did this with a hideous amount of editfiles which I should
probably
> > script; it's very prone to errors and generates a lot of stress when
> > people edit.
>
> interfaces: ?
[Wheeler, John]
I've always wanted to monkey with the "interfaces" directive. It doesn't
appear that this function updates the relevant file necessary to survive
reboot. I didn't want to have configuration information in multiple
places like ifcfg-eth0 as well as embedded in my config files so I chose
to forgo its usage optimizing on data normalization instead.
Does anyone use this?
- Re: Other possible cfengine weak areas?, (continued)
Re: Other possible cfengine weak areas?, Jamie Wilkinson, 2004/01/22
Re: Other possible cfengine weak areas?, David Douthitt, 2004/01/22
RE: Other possible cfengine weak areas?,
Wheeler, John <=