Win7/64 Bit. BOINC 6.10.18

SETI tasks are not respecting the "don't run when computer is in use" restriction ... even continue running when I suspend the project.

Is this a SETI issue, or a BOINC problem (note: SETI is the only application I see with this behavior)

Help! Want to keep SETI running but can't have it misbehaving like this

---

Win7/64 Bit. BOINC 6.10.18

SETI tasks are not respecting the "don't run when computer is in use" restriction ... even continue running when I suspend the project.

Is this a SETI issue, or a BOINC problem (note: SETI is the only application I see with this behavior)

Help! Want to keep SETI running but can't have it misbehaving like this

Hsve you (inadvertently?) set local preferences in Boinc Manager? These over-ride the web settings.

F.

---

Win7/64 Bit. BOINC 6.10.18

SETI tasks are not respecting the "don't run when computer is in use" restriction ... even continue running when I suspend the project.

Is this a SETI issue, or a BOINC problem (note: SETI is the only application I see with this behavior)

Help! Want to keep SETI running but can't have it misbehaving like this

I can't comment directly on your issue, since I do not use the "don't run when computer is in use" option.

In general, BOINC is well behaved because the science application is running at very low priority -- meaning anything else running on your machine will take priority and the science application gets what's left -- what would have otherwise gone to the "idle" task.

---

blame this guy...

---

local settings set to confirm what it should be doing (on this machine I want to restrict the hours BOINC runs) - SETI is the only app that doesn't play nice so it's been cancelled for now. Hoping I can get a pointer or clue so I can re-enable it

---

local settings set to confirm what it should be doing (on this machine I want to restrict the hours BOINC runs) - SETI is the only app that doesn't play nice so it's been cancelled for now. Hoping I can get a pointer or clue so I can re-enable it

Actually, as I understand what you're saying, the "idle" task doesn't play nice either.

---

local settings set to confirm what it should be doing (on this machine I want to restrict the hours BOINC runs) - SETI is the only app that doesn't play nice so it's been cancelled for now. Hoping I can get a pointer or clue so I can re-enable it

The first reply to you in this thread suggested you double-check your settings. Check your online preferences and make sure the computer in question is set to the right venue, or check that you are/aren't using local preferences on that machine which override the online preferences.

I have a Windows Vista x64 machine (virtually the same as Windows 7) and the suspend while in use option works correctly.

---

and I did
and it's correctly set
and it's still running when told not to :(

it's only SETI that is behaving like this on my BOINC client (running Folding@Home, ClimatePrediction and WGC as well) and it's not the first time I saw this behavior but it's much more consistent right now so it's had to get the "abort/suspend" button pressed as it's been impacting users of the machine

---

That's very strange. The BOINC client controls all the science app processing, so it's weird that BOINC properly controls the other two apps but not SETI@Home.

Thing is, I'm not sure where to begin troubleshooting this issue. Perhaps someone else will come along with an idea or two.

---

Just leave it on defaults. You shouldn't need to do anything. sounds like you'll just be compromising your overall SETI productivity.

How has it been impacting users of the machine?

That's very strange. The BOINC client controls all the science app processing, so it's weird that BOINC properly controls the other two apps but not SETI@Home.

Thing is, I'm not sure where to begin troubleshooting this issue. Perhaps someone else will come along with an idea or two.

Maybe one of the debug cc_config settings could point to the issue? I'm not sure which tho.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

it's only SETI that is behaving like this on my BOINC client

I still think Oz nailed it --> "make sure the computer in question is set to to the right venue."

Offbeat, can you pls confirm that all your projects agree on the following setting --> "Default computer location" (ex: home, school, --, work).

To really really confirm, open up for read-only your client_state.xml file, and search for all instances of "<host_venue>" --- there will be a lot in yours.

it's only SETI that is behaving like this on my BOINC client (running Folding@Home, ClimatePrediction and WGC as well)

You should at least tell us which of your hosts is affected.

Is it the one with the Nvidia card? Is the application that doesn't obey the CUDA application?

Maybe there are interactions with folding@home.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

and I did
and it's correctly set
and it's still running when told not to :(

it's only SETI that is behaving like this on my BOINC client (running Folding@Home, ClimatePrediction and WGC as well) and it's not the first time I saw this behavior but it's much more consistent right now so it's had to get the "abort/suspend" button pressed as it's been impacting users of the machine

Can you check to see if you have a file called "global_prefs.xml" file located in your BOINC Data directory (usually C:\ProgramData\BOINC for Windows 7 machines)? If so, can you please post the contents of that file here so maybe we can see what is going on?

---

That's very strange. The BOINC client controls all the science app processing, so it's weird that BOINC properly controls the other two apps but not SETI@Home.

Thing is, I'm not sure where to begin troubleshooting this issue. Perhaps someone else will come along with an idea or two.

I'm going from memory, and despite the fact that I have a smaller machine and do some pretty intense computing, I don't have BOINC stop when the user is active.

The idea is that BOINC detects user activity by monitoring the keyboard and mouse, and that task is named "boinctray."

If "boinctray" (or whatever replaced it) isn't running, then that'd explain a lot.

---

Its probably not related, but one of the PCs I have access to (4589185), would not stop running BOINC. S@H is the only project I run on BOINC. To cut a long story short, I closed BOINC as normal last night, noticed the core temps were still elevated and checked on BOINC still running. It was still running. Even after shutting down BOINC Manager through Windows Task Manager, it was still running and I had to 'shut down' the AK-V8 app through Task Manager, before it actually stopped. To be accurate, I had to stop the app, several times, because, somehow, once I'd stopped AK-V8 running, it then appears to have gone to the next task and carried on....meaning I had to repeat the process. That means that BOINC was STILL running! Nett result; errors while computing, for the first time - everything that was in the 'cache'. In this case, I am attributing the problem to Windows and the possibility that Windows Program Manager is a little 'fried'. A re-install on XP SP3 is on the cards.

---

Don't take life too seriously, as you'll never come out of it alive!

Its probably not related, but one of the PCs I have access to (4589185), would not stop running BOINC. S@H is the only project I run on BOINC. To cut a long story short, I closed BOINC as normal last night, noticed the core temps were still elevated and checked on BOINC still running. It was still running. Even after shutting down BOINC Manager through Windows Task Manager, it was still running and I had to 'shut down' the AK-V8 app through Task Manager, before it actually stopped. To be accurate, I had to stop the app, several times, because, somehow, once I'd stopped AK-V8 running, it then appears to have gone to the next task and carried on....meaning I had to repeat the process. That means that BOINC was STILL running! Nett result; errors while computing, for the first time - everything that was in the 'cache'. In this case, I am attributing the problem to Windows and the possibility that Windows Program Manager is a little 'fried'. A re-install on XP SP3 is on the cards.

sometimes when boinc manager crashes boinc.exe will still be running. It is really the application that's does most of the controlling. If it were still running that would explain what you had happening.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

That's very strange. The BOINC client controls all the science app processing, so it's weird that BOINC properly controls the other two apps but not SETI@Home.

Thing is, I'm not sure where to begin troubleshooting this issue. Perhaps someone else will come along with an idea or two.

I'm going from memory, and despite the fact that I have a smaller machine and do some pretty intense computing, I don't have BOINC stop when the user is active.

The idea is that BOINC detects user activity by monitoring the keyboard and mouse, and that task is named "boinctray."

If "boinctray" (or whatever replaced it) isn't running, then that'd explain a lot.

True, but then BOINC also wouldn't stop the other two science apps. It's still a possibility, but I'm thinking something else is amiss.

---

boinctray is running, hope the prefs give some pointers...

global_prefs_override.xml

<global_preferences>
<run_on_batteries>0</run_on_batteries>
<run_if_user_active>0</run_if_user_active>
<run_gpu_if_user_active>0</run_gpu_if_user_active>
<idle_time_to_run>3.000000</idle_time_to_run>
<start_hour>0.000000</start_hour>
<end_hour>0.000000</end_hour>
<net_start_hour>0.000000</net_start_hour>
<net_end_hour>0.000000</net_end_hour>
<leave_apps_in_memory>0</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.100000</work_buf_min_days>
<work_buf_additional_days>0.250000</work_buf_additional_days>
<max_ncpus_pct>50.000000</max_ncpus_pct>
<cpu_scheduling_period_minutes>60.000000</cpu_scheduling_period_minutes>
<disk_interval>60.000000</disk_interval>
<disk_max_used_gb>10.000000</disk_max_used_gb>
<disk_max_used_pct>50.000000</disk_max_used_pct>
<disk_min_free_gb>0.100000</disk_min_free_gb>
<vm_max_used_pct>75.000000</vm_max_used_pct>
<ram_max_used_busy_pct>5.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>50.000000</cpu_usage_limit>
</global_preferences>

global_prefs.xml

<global_preferences>
<source_project>http://bam.boincstats.com/</source_project>
<mod_time>1218078387</mod_time>
<cpu_scheduling_period_minutes>60</cpu_scheduling_period_minutes>
<idle_time_to_run>3</idle_time_to_run>
<work_buf_min_days>1.0000000</work_buf_min_days>
<work_buf_additional_days>1.0000000</work_buf_additional_days>
<max_cpus>1</max_cpus>
<cpu_usage_limit>50</cpu_usage_limit>
<disk_interval>60</disk_interval>
<disk_max_used_gb>100.0</disk_max_used_gb>
<disk_max_used_pct>50</disk_max_used_pct>
<disk_min_free_gb>1.5</disk_min_free_gb>
<vm_max_used_pct>50</vm_max_used_pct>
<ram_max_used_busy_pct>0</ram_max_used_busy_pct>
<ram_max_used_idle_pct>0</ram_max_used_idle_pct>
<max_bytes_sec_down>0</max_bytes_sec_down>
<max_bytes_sec_up>0</max_bytes_sec_up>
<start_hour>0</start_hour>
<end_hour>0</end_hour>
<net_start_hour>0</net_start_hour>
<net_end_hour>0</net_end_hour>
<hangup_if_dialed/>
<venue name="Global">
<cpu_scheduling_period_minutes>60</cpu_scheduling_period_minutes>
<idle_time_to_run>1</idle_time_to_run>
<work_buf_min_days>0.1000000</work_buf_min_days>
<work_buf_additional_days>0.0000001</work_buf_additional_days>
<max_cpus>2</max_cpus>
<cpu_usage_limit>50</cpu_usage_limit>
<disk_interval>60</disk_interval>
<disk_max_used_gb>10.0</disk_max_used_gb>
<disk_max_used_pct>50</disk_max_used_pct>
<disk_min_free_gb>1.5</disk_min_free_gb>
<vm_max_used_pct>75</vm_max_used_pct>
<ram_max_used_busy_pct>35</ram_max_used_busy_pct>
<ram_max_used_idle_pct>90</ram_max_used_idle_pct>
<max_bytes_sec_down>0</max_bytes_sec_down>
<max_bytes_sec_up>0</max_bytes_sec_up>
<start_hour>0</start_hour>
<end_hour>0</end_hour>
<net_start_hour>0</net_start_hour>
<net_end_hour>0</net_end_hour>
</venue>
<venue name="MLG">
<cpu_scheduling_period_minutes>60</cpu_scheduling_period_minutes>
<idle_time_to_run>0</idle_time_to_run>
<work_buf_min_days>1.0000000</work_buf_min_days>
<work_buf_additional_days>0.0000000</work_buf_additional_days>
<max_cpus>2</max_cpus>
<cpu_usage_limit>100</cpu_usage_limit>
<disk_interval>60</disk_interval>
<disk_max_used_gb>100.0</disk_max_used_gb>
<disk_max_used_pct>50</disk_max_used_pct>
<disk_min_free_gb>1.5</disk_min_free_gb>
<vm_max_used_pct>75</vm_max_used_pct>
<ram_max_used_busy_pct>50</ram_max_used_busy_pct>
<ram_max_used_idle_pct>90</ram_max_used_idle_pct>
<max_bytes_sec_down>0</max_bytes_sec_down>
<max_bytes_sec_up>0</max_bytes_sec_up>
<start_hour>0</start_hour>
<end_hour>0</end_hour>
<net_start_hour>0</net_start_hour>
<net_end_hour>0</net_end_hour>
<run_if_user_active/>
<hangup_if_dialed/>
</venue>
</global_preferences>

---

<venue name="Global">

<venue name="MLG">

Did you ever confirm what venues are set in client_state.xml, and which venue S@H is set to as opposed to the other projects?