Changes between Initial Version and Version 6 of Ticket #707
- Timestamp:
- Aug 3, 2008, 2:55:35 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #707
-
Property
Status
changed from
new
toreopened
-
Property
Component
changed from
Undetermined
toClient - Daemon
-
Property
Priority
changed from
Undetermined
toMajor
-
Property
Version
changed from
to
6.2.14
-
Property
Milestone
changed from
Undetermined
to6.4
-
Property
Status
changed from
-
Ticket #707 – Description
initial v6 1 This issue was brought up in [http://boinc.berkeley.edu/dev/forum_ reply.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.1 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. 2 2 3 3 I 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?