I'm thinking ... if you're logging the deletion of a lockfile, you should log the WU name in that slot for easier tracking ...

I'm thinking ... if you're logging the deletion of a lockfile, you should log the WU name in that slot for easier tracking ...

Could be but the issue is the existence of the lock file no matters what is the WU if the file exist the WU will be postponed when i restart the Boinc. That's why the way to bypass the issue is by deleting the lock file before the Boinc is restarted. I know this not fix the problem just make my host ignoring it.

---

@Jeff This is interesting:

Deleted File >> /home/juan/BOINC/slots/2/boinc_finish_called    <<<<<< -----------  look here!!!

.

Unfortunately, that's a "finish" file rather than a lockfile, so a totally different and longstanding issue. This just prevents the task from getting a "finish file not present" error when BOINC restarts. That's an issue I hope the BOINC developers will address someday.

A BOINC application in memory can sleep for as long as it likes. But it should keep just enough awareness to listen for further instructions, whether they be 'wake up and crunch', or 'exit completely, we're quitting'.

I already quit the Boinc several times after yesterday then why the "exit completely" dit not work?
Can't say for sure but not believe is't a good programing technique a program who leave "sleeping grinch" of his used data for days after it was shut down. Could not is a waste CPU time (the 13 hrs of the SSE4.1 is not a good signal) but it waste memory and whatever else it could use.
And not forget if anyone lock a slot file for any reason (cosmic ray?) it could tigger the issue.

Here's a concept. Stop using that Flawed Script that is causing problems with your previously fine working machine.
Let me guess, Jeff is the author of this script that is causing problems no others are having.
It's this flawed script you should be complaining about, instead of blaming software that works fine for everyone else.
Creating Flawed scripts and then trying to blame other people's work is a sure way to reach the Top of the Developers list of despised people.
Congratulations, it's a real feat to reach the Top of the list.

How is it you consistently ignore every piece of solid evidence presented in this thread and repeatedly spout the same asinine conclusions that have already been pretty thoroughly dismissed. You must have a really special talent.

At its simplest level, two people have reported the problem. One happens to be doing some rescheduling, one is not. Both users reporting the problem happen to be running Ubuntu 16.04 with either an AVX or AVX2 CPU app. Nobody has "blamed" any individual app, OS, or anything else, because not enough evidence has been developed yet to reach any conclusions. So, unless you care to actually contribute useful analysis and investigative effort to this issue, you should really just BUTT OUT.

Congrats again, you have assumed a permanent position.

So, even the simplest level of Analysis 101 is still too complex for you. Then please stick to putting your efforts into what you seem to be good at, which appears to be compiling programs for use in non-standard operating environments. We'll all get more benefit from that kind of effort than from your ridiculous diatribes here.

instead of blaming software that works fine for everyone else

Sorry i never blame any software, scripts or builds, just post something that was happening in my host & try to do all the tests proposed in order to try to understand why that was happening. I have the idea that's why the Number Crunching forum exists. If that was offensive to you or any other please forgive me. That's was never my intention . Don't need to be aggressive.

If anyone wish to make any additional test please PM, I will be happy do anything in my power to do the tests but I will not put anything else on this thread not believe this is the way to address who only was asking for help.

Bye all and thanks for you patience and time.

---

instead of blaming software that works fine for everyone else

Sorry i never blame any software, scripts or builds, just post something that was happening in my host & try to do all the tests proposed in order to try to understand why that was happening. I have the idea that why the Number Crunching forum exists. If that is offensive to you or any other please forgive me. That's was never my intention . Don't need to be aggressive.

If anyone wish to make any additional test please PM, I will be happy do anything in my power to do the tests but I will not put anything else on this thread not believe this is the way to address who only was asking for help.

Bye all and thanks for you patience and time.

What is this?

Can't say for sure but not believe is't a good programing technique a program who leave "sleeping grinch" of his used data for days after it was shut down. Could not is a waste CPU time (the 13 hrs of the SSE4.1 is not a good signal) but it waste memory and whatever else it could use.

I've certainly Never had what you are describing there, and as far as I know No one else has either. The one time glitch RueiKe had is similar to the one time glitch I had on my Mac, which uses the STOCK version of BOINC 7.8.4. One time glitches are Not what you are describing.
Try avoiding the script for a while and see if you get the same problems.