[Bug 836720] New: domainname on NIS server not set
https://bugzilla.novell.com/show_bug.cgi?id=836720 https://bugzilla.novell.com/show_bug.cgi?id=836720#c0 Summary: domainname on NIS server not set Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: admin@fph.physik.uni-karlsruhe.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 If a host is configured as ypserver and *not* as ypclient, the domainname is not set. The binary /bin/domainname yields "(none)". This yields that NIS-maps are stored under /var/yp/(none) per default. As far as I found out: With systemd taking over, the domainname for a NIS client is now set by /usr/share/ypbind/ypbind-systemd-pre. This script is called by /usr/lib/systemd/system/ypbind.service. If a server is not a NIS client, domainname is nowhere set. Coming off topic, please allow me a short rant: I really would prefer to have the server to be a NIS-client itsself (which makes perfect sense to me). Then I would never have encountered the described problem. But due to the unfortunate change of "pwdutils" to "shadow" (cf. openSuSE 12.3 Release Notes section 5.4) I had merge /etc and /var/yp tables. I'm really missing the "-P" option in useradd, usermod,... ! Reproducible: Always Steps to Reproduce: 1. Install NIS server 2. But no NIS client 3. look at domainname or issue /usr/bin/make -s -C /var/yp Actual Results: /bin/domainname yields (none) Expected Results: domainname should be set according to /etc/defaultdomain -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c
Ye Yuan
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c1
Thorsten Kukuk
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c2
Achim Mildenberger
The domainname was and should be set by /etc/init.d/boot.localnet. To my knowledge, /etc/init.d/boot.localnet is not executed with systemd. (Comment #2 of https://bugzilla.novell.com/show_bug.cgi?id=809553) The domainname is now set (for NIS-clients) by /usr/share/ypbind/ypbind-systemd-pre which is called from /usr/lib/systemd/system/ypbind.service
Don't know what was changed in current openSUSE versions that this don't work anymore and who is responsible for that. Maybe the change is caused by not executing /etc/init.d/boot.localnet anymore. I can't tell this for sure since I only removed the NIS-client-property of my server with release 12.3. (Due to merging /var/yp and /etc because of the missing -P switches in "pwdutils/shadow")
It's not the responsibility of ypserv to set the domainname, ypserv even does not need it. Wouldn't make sense, because ypserv can serve multiple domains, not only one. But you can set only one domainname. Yes that's a good point. But there is a dependency on the domainname, at least if one has only one domain and uses the default setup: The file /var/yp/Makefile which creates the NIS-maps for ypserv has the line LOCALDOMAIN = `/bin/domainname` So if there is only one domain, I would prefer that everything works with this one domain configured.
Greetings, Achim -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c
Ye Yuan
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c4
Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c5
--- Comment #5 from Achim Mildenberger
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c
Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c6
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c7
Thorsten Kukuk
Well, YaST should correctly write /etc/defaultdomain (am I right?)
Since yast2 nis-server allows to configure the NIS domain name, it should write that file, correct.
Than it (re)starts relevant services and than calls make.
If not ypserv, which service should take care of setting the domain name? Do you think YaST should do that directly?
systemd is now responsible for setting the domainname according to the other bug. Byt, if yast2 nis-server does not set the domainname, I wonder why it did worked in the past? At least on SLES11 SP3, ypserv does not set the domainname, too. Does yast2 nis-server call any other initscripts, too? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c8
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c9
Jiří Suchomel
(In reply to comment #6)
Well, YaST should correctly write /etc/defaultdomain (am I right?)
Since yast2 nis-server allows to configure the NIS domain name, it should write that file, correct.
My question was meant for the reporter, to ensure the file was written correctly. But I think it was.
Does yast2 nis-server call any other initscripts, too?
portmap/rpcbind, ypserv, (popssibly yppasswdd, ypxfrd, ypbind) I think nothing more. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c10
--- Comment #10 from Achim Mildenberger
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c11
--- Comment #11 from Frederic Crozat
[Install] WantedBy=multi-user.target
Without the last line, "systemctl enable domainname.service" complains and does nothing.
Bad copy-paste, I thought I had written it :( So, we need to add this file to aaa_base and also ensure it is enabled by default (in systemd-preset-brandind-openSUSE).. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c12
systemd maintainers
So, we need to add this file to aaa_base and also ensure it is enabled by default (in systemd-preset-brandind-openSUSE)..
What is the status of this one -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=836720
https://bugzilla.novell.com/show_bug.cgi?id=836720#c13
Frederic Crozat
(In reply to comment #11)
So, we need to add this file to aaa_base and also ensure it is enabled by default (in systemd-preset-brandind-openSUSE)..
What is the status of this one
File has not been pushed to aaa_base (I'm not sure I was the one who should do it) and neither the changes to systemd-preset-branding-openSUSE was done -- 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.
participants (1)
-
bugzilla_noreply@novell.com