Hi, Excerpts from Andrew Pollock's message of Fri Oct 16 22:52:04 +0200 2009: > I've just had a look at it. It's not a bug, it's working as intended. The > prepend directive allows you to override DHCP *in their entirety*. If you > use it, you need to stipulate what the entire option should contain. It > doesn't let you prepend part of a value into an option's data. Uhm, that seems a big strange to me. First of all, it is not intuitive at all to call that option prepend, if it behaves like you just said. Secondly, I want to quote the manpage:
--- If for some option the client should always use a locally-configured value or values rather than whatever is supplied by the server, these values can be defined in the supersede statement. If for some set of options the client should use a value you supply, and then use the values supplied by the server, if any, these values can be defined in the prepend statement. --- Is the manpage utterly wrong? Best regards, Michael -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
