https://bugzilla.novell.com/show_bug.cgi?id=402575
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=402575#c10
--- Comment #10 from Marius Tomaschewski
Problem solved. OpenSUSE 11 includes dhcpcd 3 (which is mentioned in the release notes) and installs a new config file /etc/dhclient.conf.rpmnew,
Please note, that the dhcpcd 3.x update mentioned in release notes is a completely different dhcp client (used by default by ifup / rcnetwork) and does not have anything to do with the dhclient (dhcp-client package) that is used by the NetworkManager. It does not touch dhclient.conf. (In reply to comment #9 from Tambet Ingo)
"(I would guess almost everybody has that problem?)"
Everybody who was using 10.3, changed /etc/dhclient.conf and upgraded to 11.0.
Yes, it looks like. The dhcp-client RPM installs it (on 11.0 as well as before) using %config(noreplace) /etc/dhclient.conf so when the user modifies it, the RPM installs dhclient.conf.rpmnew only.
How should we fix it? I don't agree with showing a dialog, it would be a bit better but wouldn't solve the issue. The only possible solution I see is to fix dhclient to override configuration file values with command line arguments (like every other program does). Marius, do you agree with this solution? Or do you have some other suggestions?
Hmm... This would be a change of the behavior of the dhclient (that is not really usual here) but sounds like the best option we have. Alternatively it would be possible to add a postinstall hook removing the script option from the (even user modified) config... not good. The third way would be to use also the -cf option in NetworkManager. The dhclient(8) manual page is not very exact about the precedence of config vs. command line: "[...] The names of the network interfaces that dhclient should attempt to configure may be specified on the command line. If no interface names are specified on the command line dhclient will normally identify all network interfaces, eliminating non-broadcast interfaces if possible, and attempt to configure each interface. It is also possible to specify interfaces by name in the dhclient.conf(5) file. If interfaces are specified in this way, then the client will only configure interfaces that are either specified in the configuration file or on the command line, and will ignore all other interfaces. [...]" Hmm... "either specified in the configuration file or on the command line". fine and which does it use when both is the case? Ignore all, use all? "[...] The DHCP client normally gets its configuration information from /etc/dhclient.conf, its lease database from /var/lib/dhcp/dhclient.leases, stores its process ID in a file called /var/run/dhclient.pid, and configures the network interface using /sbin/dhclient-script To specify different names and/or locations for these files, use the -cf, -lf, -pf and -sf flags, respectively, fol- lowed by the name of the file. This can be particularly useful if, for example, /var/lib/dhcp or /var/run has not yet been mounted when the DHCP client is started. [...]" OK, "To specify different names [...] use the -cf, -lf, -pf and -sf flags" sound clear enough for me to fix it to override the default & config values with command line options. I'll take a look on this, but not before next week. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.