[Bug 226405] New: /sbin/modify_resolvconf cleanup ignores MODIFY_RESOLV_CONF_DYNAMICALLY="no"
https://bugzilla.novell.com/show_bug.cgi?id=226405 Summary: /sbin/modify_resolvconf cleanup ignores MODIFY_RESOLV_CONF_DYNAMICALLY="no" Product: openSUSE 10.3 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: zoz@novell.com ReportedBy: mmarek@novell.com QAContact: qa@suse.de 1) Add custom nameservers to /etc/resolv.conf (eg. because the ns suggested by dhcp is lame) 2) set MODIFY_RESOLV_CONF_DYNAMICALLY=no according to comments in /etc/resolv.conf 3) forget to delete the ### BEGIN..END INFO block in /etc/resolv.conf or delete /etc/resolv.conf.saved.by.* :) 4) verify by 'rcnetwork restart' that it works 5) Reboot -> /etc/init.d/boot.cleanup will call /sbin/modify_resolvconf cleanup, which will suddenly overwrite /etc/resolv.conf by /etc/resolv.conf.saved.by.* If 5) is really the desired behaviour, could the comments in the generated /etc/resolv.conf point the user to either delete all /etc/resolv.conf.saved.by.* or delete the ### BEGIN..END INFO block? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226405 zoz@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #1 from zoz@novell.com 2006-12-10 02:31 MST ------- Yes, this was indeed desired behavior. MODIFY_RESOLV_CONF_DYNAMICALLY=no prevents modify_resolvconf from modifying resolv.conf. But it should of course clean up, what it modified. There are options for your purpose (see manpage): -o, --save_now <filename> saves the current /etc/resolv.conf (/etc/named.conf) to the specified file. This may be used if you are interested in the modification after restore or cleanup. Alternatively you can use --save_later when modifying. -k, --keep if used with restore or cleanup it keeps the current (modified) resolver settings. Since modify_cleanup worked this way now for many years i tend to not change that. Further NM is improving and will be used much more in the future. And NM does not use modify_resolvconf. And even if NM had to manage resolv.conf the same way it won't use the old shell script. (Added a note about this bug to my network setup development plan) So consider that invalid. OK? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226405 ------- Comment #2 from mmarek@novell.com 2006-12-15 08:43 MST ------- The surprising (for me) behaviour was that 'rcnetwork restart' didn't touch /etc/resolv.conf. But if it's just me who run into this, then let's leave it as invalid :-) -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com