Posts by mobluse

1) Message boards : Number crunching : SiDock tasks on Raspberry Pi keep running when waiting or suspended (Message 1629) Posted 9 May 2022 by mobluse Post: I think this is a big issue on computers I also use for e.g. browsing, because I often forget to start BOINC after I stopped it. I had to stop receiving new tasks from SiDock@home on those computers and instead use yoyo@home. I still use SiDock on dedicated BOINC computers. I reported my problems here: https://www.sidock.si/sidock/forum_thread.php?id=198&postid=1614#1614
2) Questions and Answers : Unix/Linux : BOINC-processes "cmdock -c -r target.prm" locks up the computer even though tasks are suspended (Message 1614) Posted 5 Apr 2022 by mobluse Post: My BOINC is configured to pause when I use the computer (Raspberry Pi 4 B 8 GB with Raspbian Buster 32-bit), and that works, but some other BOINC-processes runs instead at almost 100%: 16290 boinc 39 19 103M 18860 5792 R 98.9 0.2 20:50.16 cmdock -c -r target.prm -p /var/lib/boinc-client/slots/2/data/sc 16288 boinc 39 19 104M 18888 5852 R 98.2 0.2 20:55.59 cmdock -c -r target.prm -p /var/lib/boinc-client/slots/3/data/sc 16286 boinc 39 19 163M 79816 5792 R 97.6 1.0 20:45.58 cmdock -c -r target.prm -p /var/lib/boinc-client/slots/0/data/sc I copied the above from htop. In BOINCTUI it looks like this: 1 Susp. 64,11 SiDock@home 4h 4d CurieMarieDock on BOINC + zipp corona_NSP14_MTase_ 2 Susp. 47,41 SiDock@home 35m 4d CurieMarieDock on BOINC + zipp corona_PLpro_v3_sid 3 Susp. 41,85 SiDock@home 39m 4d CurieMarieDock on BOINC + zipp corona_PLpro_v3_sid 4 Run 98,41 WUProp@Home 27s 6d Data collect version 4 data_collect_v4_164 5 Wait - SiDock@home 67m 4d CurieMarieDock on BOINC + zipp corona_PLpro_v3_sid 6 Wait - SiDock@home 67m 4d CurieMarieDock on BOINC + zipp corona_PLpro_v3_sid 7 Wait - SiDock@home 67m 4d CurieMarieDock on BOINC + zipp corona_PLpro_v3_sid The computer is super slow to use. The only workaround I found is to reboot. Then it works normally for some time e.g. some days, but then this problem starts again. What is "cmdock -c -r target.prm"?