Bug 23151

Summary:	ypbind fails when /etc/yp.conf contains a valid as well invalid domain name
Product:	Gentoo Linux	Reporter:	Arun <punjarun>
Component:	[OLD] Core system	Assignee:	Brad Cowan (RETIRED) <bcowan>
Status:	RESOLVED WONTFIX
Severity:	minor	CC:	ogunden
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Arun 2003-06-19 20:12:58 UTC

I am using a gentoo distribution - with 2.4.20 on a 550Mhz/128/10 Dell Optiplex
with a P3 processor. I am using DHCP. 

My DHCP server incorrectly returned to me following domains when I booted:
[ a, b are placeholders]
a.b.com and b.com 

Where a.b.com is a valid domain but b.com is not a valid domain any longer.
=== yp.conf   start =====

domain a.b.com, a.b.com broadcast
===== yp.conf end =====

This caused /etc/init.d/ypbind to fail. Once ypfailed, the autofs too failed.

So I edited the yp.conf file and did 
  $/etc/init.d/ypbind restart 
and yp came back
up again.

First problem
==============
If one domain is incorrect it should not cause ypbind to fail completely.
Or is the format of , seperated domains not allowed in yp.conf ?

Second Problem
===============
I noticed that autofs had not come back up, even after ypbind came up. 
So tried to do 
   $/etc/init.d/autofs restart 

But it still failed.

SO I tried 
   $/etc/init.d/autofs stop
But this did not stop the service. So I had to zap the autofs service. 
I would have thought a restart should be possible.



Reproducible: Always
Steps to Reproduce:
1. Have DHCP server send back nis domains a.b.com and a.com
2. DHCP client should have a yp.conf as detailed above
3. run $ypbind -f /etc/yp.conf the yp will not come up.
4. edit /etc/yp.conf to remove the a.com 
5. run $ypbind -f /etc/yp.conf and it works fine.



Actual Results:  
After step 3 the yp did not come up

Expected Results:  
yp should have come up, with just domain a.b.com

Comment 1 Owen Gunden 2003-08-17 23:43:26 UTC

what version of ypbind are you using?  this sounds like a bug in ypbind, not the gentoo package.  maybe ypbind 1.12 fixes this issue?  or maybe a bug should be filed with the ypbind mantainer.

Comment 2 Owen Gunden 2003-08-29 05:56:17 UTC

Thorsten Kukuk (the ypbind author) says:

The syntax domain, domain is invalid. ypbind will search for
"a.com, b.com", which is a valid domainname for NIS.
ypbind is correct here, the tool writing /etc/yp.conf is wrong.
It need to write two lines in /etc/yp.conf.


Did you write the yp.conf with the comma syntax or did dhcpcd do that?

Comment 3 Owen Gunden 2004-02-24 17:54:17 UTC

Is this still a problem Arun?  I would say WONTFIX to this, if I could :).

Comment 4 Brad Cowan (RETIRED) gentoo-dev

2004-03-04 19:11:25 UTC