![]() The following NEW packages will be installed:Ġ upgraded, 3 newly installed, 0 to remove and 0 not upgraded.Īfter this operation, 6,377kB of additional disk space will be used. The following extra packages will be installed: I've set Yoyo to allow new tasks again and I'll see what happens let you know how it works out.Ĭode: Alles auswählen apt-get install boinc In the second column the permission still seems to be root, but I have no clue what's the difference between the second and third columns. I've tried to change the permissions of the files through the GUI (right-click/properties/permissions), but this doesn't change the permissions in the ls -l listingĬode: Alles auswählen ls -l /var/lib/boinc-client/projects/total 1564 If so, how can I change them to give the appropriate permissions to the Boinc account? And will Wine be able to handle that? I think it has to do with the root permission of the files I copied into the dir. rw-r-r- 1 boinc boinc 82 12:28 stat_icon For Fedora systems, add the line NETWORKWAIT=yes to /etc/sysconfig/network to delay system startup for 10 seconds or until a network connection is up, whichever occurs sooner.Code: Alles auswählen ls -l /var/lib/boinc-client/projects/total 1560. ![]() For desktops, the workaround is to introduce a delay into either the system boot procedure or the BOINC startup procedure. For laptops that lose the connection when moving from one connection to another the only workaround is to simply restart BOINC. This bug will hopefully be fixed by version 6.3.4. The proper fix is to have BOINC client check to see if the network is up and running before attempting to use it and, if it is not up and running, to check every few seconds until it is. If BOINC is able to contact your projects after the restart then you probably have this problem. To determine if you actually have this problem, restart BOINC client (just BOINC client, not the operating system) then try to update 1 or 2 projects. ![]() It will be unable to contact any of your projects. You will see the 3 messages in the above list every time BOINC client tries to contact a project to initiate a scheduler request. ![]() Scheduler request failed: Couldn't resolve host name Project communication failed: attempting access to reference siteĪccess to reference site failed - check network connection or proxy configuration. You will, in relatively short time, see all of the following error messages: It can also happen when BOINC is running on a laptop that goes into hibernation and moves from one network connection to a different connection where it comes out of hibernation. Typically, this becomes a problem when you have BOINC configured to start at boot time as a Windows service or Linux daemon service. ![]() Furthermore, BOINC is unable to use network connections that become available after it has started. BOINC client should check to see if the network is ready before attempting to use it and take appropriate measures if the network is not ready but unfortunately BOINC does not do that. You will see this problem if BOINC client starts before the network has initialised and become ready for use. This problem is caused by networking hardware (modems, routers, NICs) that initialise slowly for various reasons. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |