I want to compute a mixture of CPU/GPU projects 24/7 on my desktop computer except between 4pm and 9pm weekdays. I want to suspend computing weekdays between 4pm to 9pm.
What is the best way to configure the BOINC Manager to accomplish this?
The method I tried gives me the "no recent user activity" message and goes idle.
ACTIVITY settings:
- CPU based on Preferences, GPU Always, Network Always

I am using LOCAL PREFERENCES.
I have all the OPTIONS -> COMPUTING -> WHEN-TO-SUSPEND options unchecked.
I set the OPTIONS -> DAILY-SCHEDULES -> COMPUTING to:
- COMPUTE-ONLY-BETWEEN 21:00 and 16:00
- DAY-OF-WEEK-OVERRIDE:
Saturday and Sunday CHECKED and 00:00 to 24:00 entered in the TEXTBOXES.

With these settings, the machine gives me the "Suspending computation - no recent user activity" EVENTLOG message and stops computing.

To reproduce the problem, all I have to do is to stop keyboard/mouse input for 3 minutes. Example, I refreshed Milkyway@Home and then stop my input. The EVENTLOG lines that show the refresh and the suspend message:

4/18/2019 11:48:55 AM | Milkyway@Home | Scheduler request completed
<computing completed, upload, download message stuff clipped out>
4/18/2019 11:51:57 AM | | Suspending computation - no recent user activity
4/18/2019 11:52:17 AM | | Resuming computation



BOINC Manager Version 7.14.2 (x64)
wxWidgets Version 3.0.1
BOINC Not installed as service
Windows 10 Pro, feature update 1803

Projects: Einstein@Home MilkyWay@home PrimeGrid Rosetta@home SETI@home
World Community Grid climateprediction.net SETI@home Beta RALPH@Home

There's an option in the computing preferences called "Suspend when no mouse/keyboard input in last N minutes". Set this to --- or 0 to disable it. This is causing the message you see.

---

There's an option in the computing preferences called "Suspend when no mouse/keyboard input in last N minutes". Set this to --- or 0 to disable it. This is causing the message you see.

That is what I would think and the first thing I checked. The boxes are unchecked and the value in the "minutes" box is blank. It is almost the BOINC Manager is is ignoring the checkbox.

"I have all the OPTIONS -> COMPUTING -> WHEN-TO-SUSPEND options unchecked. "

There's an option in the computing preferences called "Suspend when no mouse/keyboard input in last N minutes". Set this to --- or 0 to disable it. This is causing the message you see.

When I turn on the EVENTLOG suspend_debug option, the messages that were displayed just before the "suspend" looked strange.


4/18/2019 1:21:35 PM | | [suspend] net_susp: no; file_xfer_susp: no; reason: unknown reason

Please post the contents of the global_prefs.xml and global_prefs_override.xml files from your BOINC data directory.

---

Please post the contents of the global_prefs.xml and global_prefs_override.xml files from your BOINC data directory.

Eventlog showing the machine restarting at "4/19/2019 9:01:37 AM". I set the "suspend_debug" and it is displaying the message below.

4/19/2019 9:01:34 AM | | [suspend] net_susp: no; file_xfer_susp: no; reason: unknown reason
4/19/2019 9:01:35 AM | | [suspend] net_susp: no; file_xfer_susp: no; reason: unknown reason
4/19/2019 9:01:36 AM | | [suspend] net_susp: no; file_xfer_susp: no; reason: unknown reason
4/19/2019 9:01:37 AM | | Resuming computation
4/19/2019 9:01:37 AM | | [suspend] net_susp: no; file_xfer_susp: no; reason: unknown reason
4/19/2019 9:01:38 AM | | [suspend] net_susp: no; file_xfer_susp: no; reason: unknown reason
4/19/2019 9:01:39 AM | | [suspend] net_susp: no; file_xfer_susp: no; reason: unknown reason


I just checked on the machine at "4/19/2019 9:01:37 AM" and it was still misbehaving the same way.
I may have changed some of the settings, but I don't seem to be able to use the schedule on this machine.
I have a Linux machine with the same version of Manager and it seems to work fine.


<global_preferences>
<source_project>http://www.worldcommunitygrid.org/</source_project>
<source_scheduler>https://scheduler.worldcommunitygrid.org/boinc/wcg_cgi/fcgi</source_scheduler>

<max_ncpus_pct>100.0</max_ncpus_pct>
<cpu_usage_limit>80.0</cpu_usage_limit>
<run_on_batteries>0</run_on_batteries>
<run_if_user_active>1</run_if_user_active>
<run_gpu_if_user_active>1</run_gpu_if_user_active>
<idle_time_to_run>3</idle_time_to_run>
<suspend_if_no_recent_input>0.0</suspend_if_no_recent_input>
<suspend_cpu_usage>25.0</suspend_cpu_usage>
<work_buf_min_days>0.1</work_buf_min_days>
<work_buf_additional_days>0.25</work_buf_additional_days>
<cpu_scheduling_period_minutes>0</cpu_scheduling_period_minutes>
<disk_interval>60.0</disk_interval>
<disk_max_used_gb>0.0</disk_max_used_gb>
<disk_min_free_gb>1.0</disk_min_free_gb>
<disk_max_used_pct>90.0</disk_max_used_pct>
<ram_max_used_busy_pct>15.0</ram_max_used_busy_pct>
<ram_max_used_idle_pct>50.0</ram_max_used_idle_pct>
<leave_apps_in_memory>1</leave_apps_in_memory>
<vm_max_used_pct>0.0</vm_max_used_pct>
<max_bytes_sec_down>0.0</max_bytes_sec_down>
<max_bytes_sec_up>0.0</max_bytes_sec_up>
<daily_xfer_limit_mb>0.0</daily_xfer_limit_mb>
<daily_xfer_period_days>0</daily_xfer_period_days>
<dont_verify_images>0</dont_verify_images>
<confirm_before_connecting>1</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
<start_hour>0</start_hour>
<end_hour>0</end_hour>
<net_start_hour>0</net_start_hour>
<net_end_hour>0</net_end_hour>
<preset>custom</preset>
<venue name="home">
<run_on_batteries>1</run_on_batteries>
<run_if_user_active>1</run_if_user_active>
<run_gpu_if_user_active>1</run_gpu_if_user_active>
<idle_time_to_run>3</idle_time_to_run>
<suspend_if_no_recent_input>3.0</suspend_if_no_recent_input>
<suspend_cpu_usage>25.0</suspend_cpu_usage>
<start_hour>0</start_hour>
<end_hour>0</end_hour>
<leave_apps_in_memory>1</leave_apps_in_memory>
<cpu_scheduling_period_minutes>60</cpu_scheduling_period_minutes>
<max_ncpus_pct>100.0</max_ncpus_pct>
<cpu_usage_limit>0.0</cpu_usage_limit>
<disk_max_used_gb>10.0</disk_max_used_gb>
<disk_min_free_gb>1.0</disk_min_free_gb>
<disk_max_used_pct>90.0</disk_max_used_pct>
<disk_interval>60.0</disk_interval>
<vm_max_used_pct>50.0</vm_max_used_pct>
<ram_max_used_busy_pct>50.0</ram_max_used_busy_pct>
<ram_max_used_idle_pct>50.0</ram_max_used_idle_pct>
<work_buf_min_days>0.1</work_buf_min_days>
<work_buf_additional_days>0.25</work_buf_additional_days>
<confirm_before_connecting>1</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
<max_bytes_sec_down>0.0</max_bytes_sec_down>
<max_bytes_sec_up>0.0</max_bytes_sec_up>
<net_start_hour>0</net_start_hour>
<net_end_hour>0</net_end_hour>
<daily_xfer_limit_mb>0.0</daily_xfer_limit_mb>
<daily_xfer_period_days>0</daily_xfer_period_days>
<dont_verify_images>0</dont_verify_images>
<preset>custom</preset>
</venue>
<mod_time>1553035566</mod_time>
</global_preferences>


OVERRIDES ..........................
<global_preferences>
<run_on_batteries>1</run_on_batteries>
<run_if_user_active>1</run_if_user_active>
<run_gpu_if_user_active>1</run_gpu_if_user_active>
<suspend_cpu_usage>0.000000</suspend_cpu_usage>
<start_hour>21.000000</start_hour>
<end_hour>16.000000</end_hour>
<net_start_hour>0.000000</net_start_hour>
<net_end_hour>0.000000</net_end_hour>
<leave_apps_in_memory>1</leave_apps_in_memory>
<confirm_before_connecting>0</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
<dont_verify_images>0</dont_verify_images>
<work_buf_min_days>0.010000</work_buf_min_days>
<work_buf_additional_days>0.010000</work_buf_additional_days>
<max_ncpus_pct>95.000000</max_ncpus_pct>
<cpu_scheduling_period_minutes>60.000000</cpu_scheduling_period_minutes>
<disk_interval>60.000000</disk_interval>
<disk_max_used_gb>0.000000</disk_max_used_gb>
<disk_max_used_pct>100.000000</disk_max_used_pct>
<disk_min_free_gb>10.000000</disk_min_free_gb>
<vm_max_used_pct>50.000000</vm_max_used_pct>
<ram_max_used_busy_pct>80.000000</ram_max_used_busy_pct>
<ram_max_used_idle_pct>90.000000</ram_max_used_idle_pct>
<max_bytes_sec_up>0.000000</max_bytes_sec_up>
<max_bytes_sec_down>0.000000</max_bytes_sec_down>
<cpu_usage_limit>100.000000</cpu_usage_limit>
<daily_xfer_limit_mb>0.000000</daily_xfer_limit_mb>
<daily_xfer_period_days>0</daily_xfer_period_days>
<day_prefs>
<day_of_week>0</day_of_week>
<start_hour>0.00</start_hour>
<end_hour>24.00</end_hour>
</day_prefs>
<day_prefs>
<day_of_week>6</day_of_week>
<start_hour>0.00</start_hour>
<end_hour>24.00</end_hour>
</day_prefs>
</global_preferences>

My apologies, the "Suspend when no mouse/keyboard input in last N minutes" option is only available on the website preferences.
So here make sure you change it in the correct venue/location for that computer.

I say that because your global_prefs.xml file shows:

<suspend_if_no_recent_input>0.0</suspend_if_no_recent_input>
<suspend_cpu_usage>25.0</suspend_cpu_usage>

for the default venue, but:

<suspend_if_no_recent_input>3.0</suspend_if_no_recent_input>
<suspend_cpu_usage>25.0</suspend_cpu_usage>

for the Home venue.

You can check the computer's location by picking it from https://setiathome.berkeley.edu/hosts_user.php, going into its details, then scrolling down to Location.

---

No apology needed. I appreciate your help. I am not sure I understand your guidance and why venue is an issue. The machine "sky2066" is the one with the problem. The machine "skyx9980xe" seems to be working as desired.

I want to disable all the suspend conditions, except TIME OF DAY. I only want to suspend during a specified 5 hour weekday "Time of Day" period from 4pm to 9pm.

My problem is that I have all the Computing -> WHEN TO SUSPEND boxes unchecked AND the ACTIVITY PREFERENCES set to "BASED ON PREFERENCES", but the machine is suspending when the keyboard is idle. Suspending when idle is just the opposite of what I want.
I want it to only suspend based on "DAILY SCHEDULES" section only.

My apologies, the "Suspend when no mouse/keyboard input in last N minutes" option is only available on the website preferences.
So here make sure you change it in the correct venue/location for that computer.

I say that because your global_prefs.xml file shows:

<suspend_if_no_recent_input>0.0</suspend_if_no_recent_input>
<suspend_cpu_usage>25.0</suspend_cpu_usage>

for the default venue, but:

<suspend_if_no_recent_input>3.0</suspend_if_no_recent_input>
<suspend_cpu_usage>25.0</suspend_cpu_usage>

for the Home venue.

You can check the computer's location by picking it from https://setiathome.berkeley.edu/hosts_user.php, going into its details, then scrolling down to Location.

Venue is an issue when you change preferences in another one than the machine with the problem is running in. You have to change the preferences in the venue/location of the problematic PC and then make sure it reads those preferences from that project to make sure it's got them. Not all preferences are set via BOINC Manager, some are still set via the web site, this being one of them.

Venue is an issue when you change preferences in another one than the machine with the problem is running in. You have to change the preferences in the venue/location of the problematic PC and then make sure it reads those preferences from that project to make sure it's got them. Not all preferences are set via BOINC Manager, some are still set via the web site, this being one of them.

If I UPDATE the PROJECT from the BOINC Manager, is that good enough to make sure the machine has read the preferences from the web? If not, are there instructions?

thanks

If I UPDATE the PROJECT from the BOINC Manager, is that good enough to make sure the machine has read the preferences from the web?

Yes

---

If I UPDATE the PROJECT from the BOINC Manager, is that good enough to make sure the machine has read the preferences from the web?

Yes

I updated all the projects and rebooted the system. The problem persisted. Made no difference.

I methodically went through all the projects and found that PrimeGrid only had a ACCOUNT -> PREFERENCES -> COMPUTING PREFERENCES profile for HOME. The system that worked used PLUTO LOCATION and the system that failed used HOME. I deleted the ACCOUNT -> PREFERENCES -> COMPUTING PREFERENCES profile for HOME and now both systems use the DEFAULT.
The problem seems to have been eliminated.

Thanks.