Entries which are not names of actual users are ignored (e.g., Shared, Deleted Users.) The installer will delete the Login Item for each user listed in the file. Ls /Users > "/Library/Application Support/BOINC Data/nologinitems.txt"Īfter creating this file, run the installer. This should be a plain text file containing a list of users to be excluded from auto-launch, one user name per line.Īn easy way to create this file is to type the following in terminal, then edit the file to remove unwanted entries: You can override this behavior by removing the BOINC Manager Login Item for selected users, either via the Accounts System Preferences panel or by creating a nologinitems.txt file in the BOINC Data folder. ![]() See Client security and sandboxing for more information.īy default, BOINC Manager starts up automatically when each user logs in. Due to the Manager's internal permissions, you can move it but cannot copy it. If you wish to block some users from using BOINC Manager, move it out of the /Applications directory into a directory with restricted permissions.Normally, BOINC Manager starts up automatically when each user logs in.You may need BOINC version 6.2 or later to work properly as a daemon. ![]() The following apply to the full GUI installation (BOINC Manager):.The BOINC Client may not successfully detect the presence of a GPU, so BOINC Project applications may not be able to use the GPU.However, older style (version 5) application graphics (including screen saver graphics) are not available when the Client runs as a daemon. Most projects have upgraded their graphics to version 6 and will display graphics properly on BOINC version 6.2 and later even when running as a daemon.Quitting the BOINC Manager will not cause the Client to exit.However, it still observes the Activity settings as set by the Manager or the boinc_cmd application (Run always, Run based on preferences, Suspend, Snooze Network activity always available, Network activity based on preferences, Network activity suspended.) The BOINC Client always runs even when no user is logged in.(If you don't use the boinc daemon that came with the GUI installation, you should check the /Library/LaunchDaemons/ file that the Make_BOINC_Service.sh script generates for double slashes (//) and remove them if necessary.) It can be used with either full GUI installations (BOINC Manager) or the stand-alone BOINC Client. ![]() Make_BOINC_Service.sh is a command-line shell script to set up the BOINC Client to run as a daemon at system startup. Running BOINC as a daemon or system service 6 Installing BOINC on a Mac using the command line.5 Selecting which users may run BOINC Manager.4 Moving BOINC Manager or BOINC Data Folder to a Different Drive.3 Using BOINC's security features with the stand-alone BOINC Client.2 Disabling auto-launch of BOINC Manager.1 Running BOINC as a daemon or system service.↳ V7.6.x Public Release Windows/Linux/MacOS X.Now I see that folding CPU tasks cannot share a thread with other busy tasks. Now CPU tasks on that one are completing in hours rather than showing insane estimates of 2-14 days. So as an experiment, I configured one of the workstations running GPU tasks and added a CPU slot with thread count as -1. And the processing speed was dramatically faster than previously. When I recently sold an older GPU and was running one system with no GPU slot and only a CPU slot, I finally had a machine completely dedicated to folding. So then I went back to BOINC for CPU tasks or just idled the CPU. But the performance of the CPU folding tasks was extremely slow and some looked like they wouldn't finish before the expiration cutoff. But my past experience with BOINC projects and Xeons with 14 cores was that it wasn't a problem to have all the threads processing work units with no impact to the GPU thread. When left at -1, it excludes one thread to feed the GPU slot. I usually overrode the thread count setting of the CPU folding slot to use all available threads rather than leave it at -1 to configure itself. But I've occasionally tried folding on CPU again when the BOINC projects have outages or lack work to distribute. I started out on CPU in the beginning before I owned any GPUs.Īfter acquiring some older Xeon workstations and some GPUs for folding, I switched over to various BOINC projects for CPU work. Over the last few years, I've been mostly folding on GPU.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |