After up to 3 consecutive files have failed it also backs off on the project for a different semi-random period of time. When an upload fails BOINC backs off on that file for a semi-random period of time. It also appears that once a host has a large number of pending uploads it stops requesting new work, which is perfectly reasonable when it is genuinely impossible to upload any of the files. If one of the upload servers is down (currently the case) the project back off mechanism can result in no uploads being possible to the other servers. > if ( log_flags.CPDN has a number of upload servers (currently 9) which accept specific upload files from different application types. XScreenSaverAllocInfo just returns a small > static XScreenSaverInfo* xssInfo = XScreenSaverAllocInfo() > // If we can connect to at least one DISPLAY, this is set to false. > const vector display_values = X_display_values_initialize() > * for all Xservers on a machine when the Xservers start up. > * One may drop a file in /etc/X11/Xsession.d/ that runs the xhost command > * access isn't available for an Xserver, then that Xserver is skipped. > * granted access to the Xservers a la "xhost +SI:localuser:boinc". This function assumes that the boinc user has been However, if even one Xserver reports busy/non-idle, then > * Return true if the idle time exceeds idle_threshold for all accessible > /* Ask the X server for user idle time (using XScreenSaver API) > const vector X_display_values_initialize(). > // Initializer for const vector in xss_idle > strlcat(p_model, cpu_type_name, sizeof(p_model)) strlcpy(p_model, "Alpha ", sizeof(p_model)) > #include "log_flags.h" // idle_detection_debug flag for verbose output > // (There is a DirScanner class in BOINC, but it doesn't do what we want) > // prevents naming collision between X.h define of Always and boinc's $ diff boinc_7.6.22_hostinfo_unix.cpp boinc_7.6.33_hostinfo_unix.cpp Please refer to what I wrote about packaged versions of BOINC.Īs GPU computing is allowed and a capable GPU is found you will always see three science processes started. The regular BOINC client sets the process priority to lowest when starting any science application and therefore this shouldn't interfere with normal operations. What shouldn't happen is that the computer is slowed down by the science apps. This should be identified by the log messages. If the user is just watching a movie and not doing anything the System thinks that the computer is unused. If the user is still using the computer (mouse/keyboard activity) than this clearly is a bug. Next question is about re-enabling computation after 45 minutes. The flags suspend_debug and task_debug may be helpful in your case. To your question of a more verbose output you should look at the user wiki ( ) where you can find log_flags that are helpful in this case.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |