conflicting command line options and dhcp.conf statements

Andrew Pollock apollock at
Tue May 16 20:43:00 UTC 2006

On Tue, May 16, 2006 at 09:48:50AM -0700, Ted Lemon wrote:
> On Tuesday 16 May 2006 05:07, Joe Bill wrote:
> >  Isn't  the purpose of command line options precisely to override specific
> >  predefined options like those belonging to a bigger set like the one
> >  specified at compile time or the one called up in a configuration file ?
> That's like saying isn't the purpose of argc and argv to provide filenames to 
> a filter so it doesn't have to read from stdin.   In one sense, perhaps yes, 
> but generally speaking no, there's no such convention.
> Historically what happened here is that I got tired of typing those things on 
> the command line when debugging, and added config file statements for them so 
> I wouldn't have to type them on the command line anymore.   So I never 
> realized that I'd done the opposite of what you think is the correct 
> behavior.

I know of multiple people who get extremely cranky about dhclient's
behaviour where it ignores interfaces on the command line in favour of
interfaces mentioned in the config file.




More information about the dhcp-users mailing list