Bug 113774 - unable to configure NIS master server using yast
Summary: unable to configure NIS master server using yast
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 3
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Jiří Suchomel
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 97395
  Show dependency tree / graph
 
Reported: 2005-08-29 09:31 UTC by Martin Mrazik
Modified: 2005-08-30 06:55 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
yast2 logs (219.50 KB, application/x-tgz)
2005-08-29 09:31 UTC, Martin Mrazik 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Mrazik 2005-08-29 09:31:00 UTC 
Using yast2-nis-server I'm unable to configure NIS master server. The yast  
"Create NIS Master Server" dialog finishes with no errors but after that the  
server is configured as a "Slave". Yast gives no error and/or information to 
the user why the server is not configured as a master.   
y2logs attached.
Comment 1 Martin Mrazik 2005-08-29 09:31:59 UTC 
Created attachment 47936 [details]
yast2 logs
Comment 2 Jiří Suchomel 2005-08-29 10:33:19 UTC 
What do you mean by writing "server is configured as a "Slave"". Is it really
configured that way or does yast2-nis-server say it when running again?
Comment 3 Martin Mrazik 2005-08-29 10:47:41 UTC 
yast2-nis server says it after running it again.      
   
Actually how can I find out that the server is really running slave? I just   
shall test the yast2-nis-server package but the testcases (from pdb) are   
rather brief and I'm quite new to NIS.    
   
However it is still confusing because the yast says something I would not   
expect.
Comment 4 Jiří Suchomel 2005-08-29 10:55:56 UTC 
Thanks for info; I'll try to reproduce it (which should be easy as I remember
this as a long problem).
Comment 5 Jiří Suchomel 2005-08-29 11:07:48 UTC 
could I login to your machine and do some tests?
Comment 8 Martin Mrazik 2005-08-30 06:07:19 UTC 
dhcp44:~ # /usr/lib/yp/yphelper --hostname 
dhcp44.suse.cz 
dhcp44:~ # /usr/lib/yp/makedbm -u /var/yp/suse.cz/group.byname 
YP_INPUT_NAME   /etc/group 
users   users:x:100: 
nobody  nobody:x:65533: 
YP_OUTPUT_NAME  /var/yp/suse.cz/group.byname 
haldaemon       haldaemon:!:102: 
nogroup nogroup:x:65534:nobody 
YP_MASTER_NAME  dhcp44.suse.cz 
YP_LAST_MODIFIED        1125307686 
messagebus      messagebus:!:101: 
dhcp44:~ #
Comment 11 Jiří Suchomel 2005-08-30 06:30:26 UTC 
Thanks, now I can see the problem.

(Bow you have patched version on your machine :-))
Comment 12 Jiří Suchomel 2005-08-30 06:55:45 UTC 
fixed in yast2-nis-server-2.12.3