Send dhcp-users mailing list submissions to
[email protected]
Advertising
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. Re: Using custom variable to assign value to bootfile-name
(Simon Hobson)
2. Re: Using custom variable to assign value to bootfile-name
(Niall O'Reilly)
----------------------------------------------------------------------
Message: 1
Date: Wed, 11 Nov 2015 22:42:55 +0000
From: Simon Hobson <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: Using custom variable to assign value to bootfile-name
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Niall O'Reilly <[email protected]> wrote:
> Variables don't do what you need.
>
> I'ld suggest something like this, repeated for the other groups:
>
> group target_1 {
> option boot-filename = "soft_1.tar";
> }
I think the problem he has is that if he allows the devs to edit that
themselves, they screw up the rest of the config. I'm wondering if some include
files (and perhaps some scripts) might work.
group target_1 {
$INCLUDE soft1.cfg
}
Then generate a number of config files that you can use with the include
statements. Either let the devs edit them directly, or let them work through a
script that does some sanity checking.
Or put placeholders in the config, and have a script that replaces them with
the desired values to generate a config file for the server to use.
------------------------------
Message: 2
Date: Thu, 12 Nov 2015 10:46:57 +0000
From: "Niall O'Reilly" <[email protected]>
To: Users of ISC DHCP <[email protected]>
Subject: Re: Using custom variable to assign value to bootfile-name
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8
On Wed, 11 Nov 2015 22:42:55 +0000,
Simon Hobson wrote:
>
> I think the problem he has is that if he allows the devs to edit that
> themselves, they screw up the rest of the config.
Ah! Sorry: I missed that.
> I'm wondering if some include files (and perhaps some scripts) might work.
>
> group target_1 {
> $INCLUDE soft1.cfg
> }
>
> Then generate a number of config files that you can use with the include
> statements. Either let the devs edit them directly, or let them work through
> a script that does some sanity checking.
>
> Or put placeholders in the config, and have a script that replaces them with
> the desired values to generate a config file for the server to use.
>
All good ideas.
/Niall
------------------------------
_______________________________________________
dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users
End of dhcp-users Digest, Vol 85, Issue 14
******************************************
