Craig White wrote:
On Sat, 2008-06-28 at 16:19 -0400, William Case wrote:
If it can't I will try Patrick's Network Manager solution.
If that works, I then have to decide whether this is a Network Manager
bug; a Boinc bug; or both. Of course, if boincmgr does successfully
reconnect to WCG and download additional work units, I will write the
whole thing off as my screwing around too much while Boinc was just
trying to do its thing.
----
service boinc restart
a relatively simple fix.
If you were to file a bug report, I would file it against NetworkManager
as this would mean that boinc works when networking is fully functional.
If the analysis of NM starting too late in the boot process is correct,
wouldn't one of these make life a bit more tolerable? Keeping in mind that
I don't use F9, NM, or BOINC. :-)
1. Change the script number in /etc/init.d of NM to a lower number than
BOINC or change BOINC number to one higher than NM.
2. Do not configure BOINC to start a boot time in the usual manner but
add a "server boinc start" to rc.local.
--
They also surf who only stand on waves.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
