Dear MAC users, currently we have not official apple developer account, thus we can not issue mac version. If some one has idea to help us to solve this issue please contact jukic dot marko at gmail dot com ;-)

I have helped Natalia to get the macOS RXDock application get to work. - See thread above. How can I help you?

@Gemini8/Jens is there a chance your Lion is 32 bit instead of 64 bit? The SiDock app appears to need 64 bit.

Thanks for your input. Seems to clear up, not solve this issue.
The kernel and Boinc run in 32-bit, the rest in 64-bit.
Can't change anything about the kernel, but I'd think it should be possible to run Boinc in 64-bit.
Will have a look at all those config xml-files.

---

- - - - - - - - - -
Greetings, Jens

I found a new issue on macOS : the tasks do not suspend.

If I tell boinc to suspend processing globally, boinc "thinks" all is suspended but the tasks actually continue to run !

I will try to fix that, it is an old bug :)

Thanks !

Note that this only happens with Curie tasks, the RxDock do suspend properly.

Hi Natalia

I recently did again some SiDock on my Mac and there is still the same behavior : I have several projects running at the same time, boinc decided to suspend the sidock tasks because there were other tasks to move to high priority run (deadlines...) and I realized the sidock that were clearly in wait state in the boinc manager actually continued to run in memory...

If it can help, now I have some normally crunching sidocks at the moment (together with wanless tasks and QChemPedIA VB tasks)



and as you can see in the process monitor all is nicely sorted "inside" boinc process, itself being "inside" the boinc manager, however in my CPU monitoring tool (iStats Menu) they appear "outside" of boinc



Normally in iStat I only have one row called "boinc manager" with the sum of all CPU used by all the boinc tasks running, not with "some of the boinc tasks out of that sum".

So I think there is "something wrong" in the way boinc is running these sidock tasks, probably due to how these tasks are "self declared to the OS" inside of the code of the sidock curie application.