Once the assimilators have catched up, they should reenable the ghost resending mechanism on the servers (the full version of it), the servers should now be able to handle that additional load.

I'll second that motion.

Meow!

Perhaps you can send a message to Eric like you did in the past (IIRC).

I shall ask him about it.

Meow!

---

"Time is simply the mechanism that keeps everything from happening all at once."

Ah, we're back.
I was getting nothing but a dozen or so messages about missing drives on Carolyn for a while there.

Just happened again. Back seconds later. :-)

Once the assimilators have catched up, they should reenable the ghost resending mechanism on the servers (the full version of it), the servers should now be able to handle that additional load.

I'll second that motion.
Meow!

. . Sadly I have no ghosts to resend ...

Stephen

:(

Once the assimilators have catched up, they should reenable the ghost resending mechanism on the servers (the full version of it), the servers should now be able to handle that additional load.

I'll second that motion.

Meow!

Perhaps you can send a message to Eric like you did in the past (IIRC).

I shall ask him about it.

Meow!

Who you gonna call?
Eric's Ghostbuster.

God I really hate PowerShell.

while ($true)
 { Get-Content C:\ProgramData\BOINC\stdoutdae.txt | Select-String -Pattern "got [0-9]*.*new tasks"
 Start-Sleep -Seconds 10  }

Things are just more elegant in nix.

while :; do clear; grep "got [0-9]*.*new tasks" ~/BOINC\ Data/stdoutdae.txt; sleep 10; done

But I can cycle through all the machines in a screen session, and get the answers across the board.

Things are just more elegant in nix.

while :; do clear; grep "got [0-9]*.*new tasks" ~/BOINC\ Data/stdoutdae.txt; sleep 10; done

There is a bug in your regexp. It matches anything that a simple "got .*new tasks" would have matched. A pattern that can match an empty string is useless just before a .*

Things are just more elegant in nix.

while :; do clear; grep "got [0-9]*.*new tasks" ~/BOINC\ Data/stdoutdae.txt; sleep 10; done

There is a bug in your regexp. It matches anything that a simple "got .*new tasks" would have matched. A pattern that can match an empty string is useless just before a .*

no, it matches anything with any number of numbers including none, then anything followed by new tasks. It gets what I want out of the file. I could have simplified it to got.*new tasks, and I have no idea what these programmers might have stuck in the stderr. My way would have matched "got [7] errors retrieving new tasks", so that is the weakness, but could be interesting to my purposes even though it isn't intended I also could have explicitly stated [0-9][0-9]* to force at least one digit, or put min/max limiters on it, but why? It could be considered a little sloppy, but I've run across instances where a programmer might sometimes forget to put a space between things, and the numbers where they are are a self-commenting idea that I EXPECT a digit, or group of digits, there (not require), followed by some random number of random bytes followed by the final part of the phrase.

Ville Saari meant that "got [0-9]*.*new tasks" matches the exact same things as "got .*new tasks": the "[0-9]*" pattern is redundant in the regexp.

---

Gazing at the skies, hoping for contact... Unlikely, but it would be such a fantastic opportunity to learn.

My alternative profile

no, it matches anything with any number of numbers including none, then anything followed by new tasks

"Someting that can be none followed by anything" is exactly the same thing as just "anything" because "anything" covers that something too. Simple logic.

If the something was such a something that excluded an empty string, then it wouldn't be redundant as it would limit the matched things to those that start with this something. But if the something matches an empty string, then it has absolutely no effect because everything starts with an empty string.

no, it matches anything with any number of numbers including none, then anything followed by new tasks

"Someting that can be none followed by anything" is exactly the same thing as just "anything" because "anything" covers that something too. Simple logic.

If the something was such a something that excluded an empty string, then it wouldn't be redundant as it would limit the matched things to those that start with this something. But if the something matches an empty string, then it has absolutely no effect because everything starts with an empty string.

bug is unintended. I fully intended it to be just this way. As I stated, I EXPECT a digit or group of digits, but I'm not requiring it. I could have shortened it, but chose not to for my own purposes.

The outcome is the same as you can clearly see

11-Apr-2020 20:56:35 [SETI@home] Scheduler request completed: got 0 new tasks
11-Apr-2020 23:40:31 [SETI@home] Scheduler request completed: got 0 new tasks
12-Apr-2020 04:25:31 [SETI@home] Scheduler request completed: got 0 new tasks
12-Apr-2020 05:02:55 [SETI@home] Scheduler request completed: got 0 new tasks
12-Apr-2020 05:57:36 [SETI@home] Scheduler request completed: got 0 new tasks

But I leave the door open to capture every other event, including events I didn't intend. That leaves me able to catch possible outcomes I might just be interested in, and outcomes I didn't plan on. At the same time, if I look at the code, I know exactly the purpose for which I originally intended it without having to leave any comments in the code to muck up my command line history. If I were to write this in a script, perhaps not so much a big deal to leave comments. Same if I wrote it into a command line function. I know what this is on sight.

Let the cleanup commence on Monday afternoon.

For the cleanup to commence do we not require tasks to timeout and then be re-sent?

---

Let the cleanup commence on Monday afternoon.

For the cleanup to commence do we not require tasks to timeout and then be re-sent?

It depends on "bunkering" hosts like this https://setiathome.berkeley.edu/results.php?hostid=8652081&offset=52360&show_names=0&state=1&appid=

Over 52K tasks in progress, with the oldest ones from 4th March !
My Android machine has 8 tasks pending, 7 of them are waiting on https://setiathome.berkeley.edu/show_host_detail.php?hostid=8652081

Let the cleanup commence on Monday afternoon.

For the cleanup to commence do we not require tasks to timeout and then be re-sent?

It depends on "bunkering" hosts like this https://setiathome.berkeley.edu/results.php?hostid=8652081&offset=52360&show_names=0&state=1&appid=

Over 52K tasks in progress, with the oldest ones from 4th March !
My Android machine has 8 tasks pending, 7 of them are waiting on https://setiathome.berkeley.edu/show_host_detail.php?hostid=8652081

Cut him some slack, he's busy telling everyone else what they're doing wrong.

Let the cleanup commence on Monday afternoon.

For the cleanup to commence do we not require tasks to timeout and then be re-sent?

It depends on "bunkering" hosts like this https://setiathome.berkeley.edu/results.php?hostid=8652081&offset=52360&show_names=0&state=1&appid=

Over 52K tasks in progress, with the oldest ones from 4th March !
My Android machine has 8 tasks pending, 7 of them are waiting on https://setiathome.berkeley.edu/show_host_detail.php?hostid=8652081

I read what you are saying. For these to be re-sent though unless there is intervention from from admin staff tasks have to reach their expiry date don't they?

---

Let the cleanup commence on Monday afternoon.

For the cleanup to commence do we not require tasks to timeout and then be re-sent?

It depends on "bunkering" hosts like this https://setiathome.berkeley.edu/results.php?hostid=8652081&offset=52360&show_names=0&state=1&appid=

Over 52K tasks in progress, with the oldest ones from 4th March !
My Android machine has 8 tasks pending, 7 of them are waiting on https://setiathome.berkeley.edu/show_host_detail.php?hostid=8652081

No wonder the servers were having kittens. :-O

Cheers.

Let the cleanup commence on Monday afternoon.

For the cleanup to commence do we not require tasks to timeout and then be re-sent?

It depends on "bunkering" hosts like this https://setiathome.berkeley.edu/results.php?hostid=8652081&offset=52360&show_names=0&state=1&appid=

Over 52K tasks in progress, with the oldest ones from 4th March !
My Android machine has 8 tasks pending, 7 of them are waiting on https://setiathome.berkeley.edu/show_host_detail.php?hostid=8652081

I read what you are saying. For these to be re-sent though unless there is intervention from from admin staff tasks have to reach their expiry date don't they?

Well the owner of that machine is a very active poster in NC, including this thread, I wonder if he would like to comment on how long it will be before his"bunker" will be empty !

Let the cleanup commence on Monday afternoon.

For the cleanup to commence do we not require tasks to timeout and then be re-sent?

It depends on "bunkering" hosts like this https://setiathome.berkeley.edu/results.php?hostid=8652081&offset=52360&show_names=0&state=1&appid=

Over 52K tasks in progress, with the oldest ones from 4th March !

And as far as GPUs, 1337 reported via spoofing, only 1 actually installed. What a special guy.

---

Well the owner of that machine is a very active poster in NC, including this thread, I wonder if he would like to comment on how long it will be before his"bunker" will be empty !

The answer is the only one that matters

“Before the deadline”

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

God I really hate PowerShell.

while ($true)
 { Get-Content C:\ProgramData\BOINC\stdoutdae.txt | Select-String -Pattern "got [0-9]*.*new tasks"
 Start-Sleep -Seconds 10  }

Things are just more elegant in nix.

while :; do clear; grep "got [0-9]*.*new tasks" ~/BOINC\ Data/stdoutdae.txt; sleep 10; done

But I can cycle through all the machines in a screen session, and get the answers across the board.

. . Both are gobbledy gook to me ... :)

Stephen

LOL