Questions and Answers :
Macintosh :
Boinc Menubar and web defaults
Message board moderation
Author | Message |
---|---|
William L Send message Joined: 15 May 99 Posts: 1 Credit: 0 RAC: 0 |
I've made my defaults (on the web site) to have Boinc run after 5 mins. of inactivity. It appears that Boinc Menubar overrides these settings since either Boinc is 'Start' or 'Stop' and never starts after 5 mins. of inactivity. (I've edited my web prefs and hit 'Update' and restarted Menubar) How do I get Menubar to wait for 5 mins. of inactivity to begin processing? |
ph0enix Send message Joined: 27 Mar 05 Posts: 11 Credit: 0 RAC: 0 |
same here, too: Mac OS X 10.3.8, BOINC client 4.19 and 4.25 (I've tried both) and BOINC Menubar 4.25a (0.2b). My defaults are to run after 15 min. of inactivity, but BOINC Menubar seems to ignore this. I have updated my preferences via the Web interface multiple times, without luck. Even the 'global_prefs.xml' file which is located under ~user/Library/Application Support/Boinc Data/ remains untouched. |
ph0enix Send message Joined: 27 Mar 05 Posts: 11 Credit: 0 RAC: 0 |
Update: It seems to me that the problem is not BOINC Menubar, it's the client: Even when starting from the command-line, the clients starts processing immediately... |
Paul Nieland Send message Joined: 18 Mar 01 Posts: 12 Credit: 0 RAC: 0 |
> My defaults are to run after 15 min. of inactivity, but BOINC Menubar seems to > ignore this. I have updated my preferences via the Web interface multiple > times, without luck. Even the 'global_prefs.xml' file which is located under > ~user/Library/Application Support/Boinc Data/ remains untouched. In other words... Boinc for the Mac s**ks ! |
Aleksander Szablewski Send message Joined: 3 Apr 99 Posts: 34 Credit: 5,133,740 RAC: 0 |
Mac client simply works on lowest priority meaning it's stopped automatically when other tasks require CPU time. Thus idle settings are not applicable - they're for Windows client. |
ph0enix Send message Joined: 27 Mar 05 Posts: 11 Credit: 0 RAC: 0 |
Ok, thanks for your answer. But I would like to decide when the client should start its work and when not. I don't like this 'It-must-running-all-the-time' behavior. So, when there's no other solution I'll remove it. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.