[Bug 972111] New: yast2 nis doesn't remove broadcast option
http://bugzilla.suse.com/show_bug.cgi?id=972111 Bug ID: 972111 Summary: yast2 nis doesn't remove broadcast option Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: robert.simai@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- noticed this on openSUSE 13.2, yast is current (3.1.109.2). Yast's nis module sets the broadcast option if desired but doesn't remove it when it's run without the checkbox marked. To duplicate: * run yast2 nis * configure some nis servers * check "broadcast" * save /etc/sysconfig/network/config contains NETCONFIG_NIS_STATIC_SERVERS_1="broadcast" and the option is set in /etc/yp.conf * run yast2 nis * save without the broadcast checkbox marked * the option still is in config and consequently in yp.conf -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=972111 http://bugzilla.suse.com/show_bug.cgi?id=972111#c1 Karl Eichwalder <ke@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ke@suse.com --- Comment #1 from Karl Eichwalder <ke@suse.com> --- I'm wondering whether it would be appropriate to add a warning? If your local DHCP server announces NIS servers, do not lookup a NIS server on your own and leave the field empty. (Or something similar.) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=972111 http://bugzilla.suse.com/show_bug.cgi?id=972111#c2 --- Comment #2 from Stefan Hundhammer <shundhammer@suse.com> --- (In reply to Karl Eichwalder from comment #1)
I'm wondering whether it would be appropriate to add a warning?
If your local DHCP server announces NIS servers, do not lookup a NIS server on your own and leave the field empty.
(Or something similar.)
Not sure if this would actually be helpful to many users; IMHO it would confuse them even more. Maybe that YaST module should catch that case and explicitly ask the user if he really wants to override the NIS server announced by DHCP when it receives that announcement. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=972111 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsuchome@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=972111 http://bugzilla.suse.com/show_bug.cgi?id=972111#c3 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers@suse.de |jsuchome@suse.com --- Comment #3 from Stefan Hundhammer <shundhammer@suse.com> --- Jiri, are you still maintaining this yast2-nis-client module? "osc maintainer" says so. If not, please reassign back. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=972111 http://bugzilla.suse.com/show_bug.cgi?id=972111#c4 Stefan Hundhammer <shundhammer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jsuchome@suse.com |yast-internal@suse.de --- Comment #4 from Stefan Hundhammer <shundhammer@suse.com> --- Now tracking in Trello: https://trello.com/c/3fQpNbdl -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=972111 http://bugzilla.suse.com/show_bug.cgi?id=972111#c5 Tomáš Chvátal <tchvatal@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Tomáš Chvátal <tchvatal@suse.com> --- This version of openSUSE changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE, or consider the bug still valid, please feel free to reopen this bug against that version, or open a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com