id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
707	detect network availability	Dagorath	davea	This issue was brought up in [http://boinc.berkeley.edu/dev/forum_thread.php?thread=2896 this thread].  Summarising, the user starts BOINC client as a daemon during boot on a Fedora 9 system that apparently brings up the network rather slowly. When BOINC client starts it finds no network available.  Putting a 15 second delay in the system startup scripts to delay starting the BOINC daemon fixed the problem for the user.\r\n\r\nI imagine BOINC client, when it starts, checks if the network is available before proceeding.  Perhaps the OS (Fedora 9) is reporting incorrectly?  Perhaps the OS reports correctly but BOINC times out too quickly?     	Defect	new	Major	Undetermined	Client - Daemon	6.6.37			mjakubicek