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.