>Number:         36171
>Category:       misc
>Synopsis:       routing daemon started after ypbind -> ypbind will hang
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    misc-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Thu Apr 19 15:00:00 +0000 2007
>Originator:     wgstuken@nagler-company.com
>Release:        NetBSD 3.1
>Organization:
Dr. Nagler & Company GmbH
>Environment:
	
	
System: NetBSD test-s3 3.1 NetBSD 3.1 (NSW-S201) #5: Wed Apr 18 13:33:24 CEST 2007 wgstuken@s012:/export/NetBSD-3.1/N+C-build/.OBJDIR_amd64/export/NetBSD-3.1/src/sys/arch/amd64/compile/NSW-S201 amd64
Architecture: x86_64
Machine: amd64
>Description:
	During system-startup the ypbind is started before the routing information of the
	system has been initialized - e.g. routed is started.
	ypbind will try to bind to the default domain and if the yp-Server is not on the local
	network, it will fail to send the request due to missing routing information.
	It is not a solution to trust any optional default-route entry, because you loose the
	ability to have redundant routing ways to "the rest of the world".

	There is a workaround by setting up a default route in rc.conf.  This workaround will
	work as long as the configured gateway is up and running at boottime and will fail if
	it is down.
>How-To-Repeat:
	Configure ypbind to use a ypserver not on the local network, try to use e.g. routed to
	get the routing information from the network and setup no default route in rc.conf.
>Fix:
	The start-order of the rcfiles need to be changed so that the network is fully functional before
	any deamons are started that need a working network.

>Unformatted: