I was trying to pass on the b and o command line parameters, so I did just what I normally do in Windows ....[GUPPIRescheduler -b -o] WRONG! You have to use the linux command line syntax. [GUPPIRescheduler --b --o] I keep forgetting you have to use those double hyphens before a parameter in linux.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I was trying to pass on the b and o command line parameters, so I did just what I normally do in Windows ....[GUPPIRescheduler -b -o] WRONG! You have to use the linux command line syntax. [GUPPIRescheduler --b --o] I keep forgetting you have to use those double hyphens before a parameter in linux.

. . Yep Keith, it does get confusing (well to me at least).

. . So have you managed to get it to actually reschedule anything ???

Stephen

??

. . I really, really do not understand the work scheduler/server arrangement at SETI.

. . Both of my Linux machines are getting a significant run of GBT tasks at the moment, so I opened up the cache of the Windows machine to hoepfully get a run of them as well and bloooeey, a huge run of Arecibo tasks. How many servers are there and are they on the same planet? It is like they are worlds apart and the different machines will only access a particular server.

Stephen

:(

I was trying to pass on the b and o command line parameters, so I did just what I normally do in Windows ....[GUPPIRescheduler -b -o] WRONG! You have to use the linux command line syntax. [GUPPIRescheduler --b --o] I keep forgetting you have to use those double hyphens before a parameter in linux.

. . Yep Keith, it does get confusing (well to me at least).

. . So have you managed to get it to actually reschedule anything ???

Stephen

??

Hi Stephen, unfortunately ..... no. I think the issue is the plan class and the CUDA80 tasks. I don't think the Rescheduler know how to handle them. I bet if you weren't running the special app and just mainstream SoG app, that the reschedule would work just as it usually does in Windows. Mr. Kevvy will have to chime in here to straighten the confusion out I think.

root@Darksider:/home/keith/Desktop/BOINC_7.8# ./GUPPIRescheduler
Mr. Kevvy's GUPPI Rescheduler v0.51 - (c)2016 Kevin Dorner

Reading configuration files...
Found sched_request GPU platform=x86_64-pc-linux-gnu app_version=0 version_num=801
CPU platform=x86_64-pc-linux-gnu app_version=2 version_num=801 and GPU plan_class=cuda80
Searching for and moving workunits in client state...
No non-GUPPI workunits are assigned to CPU to move to GPU; no changes made.
root@Darksider:/home/keith/Desktop/BOINC_7.8# 

And yes, there are non-GUPPI tasks assigned to the CPU.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

. . I really, really do not understand the work scheduler/server arrangement at SETI.

. . Both of my Linux machines are getting a significant run of GBT tasks at the moment, so I opened up the cache of the Windows machine to hoepfully get a run of them as well and bloooeey, a huge run of Arecibo tasks. How many servers are there and are they on the same planet? It is like they are worlds apart and the different machines will only access a particular server.

Stephen

:(

I've suspected ever since I put the Ryzen system online, that the servers direct tasks specifically toward hosts with specific hardware. What you've observed on your own hosts does not surprise me at all. I think the servers run by their own inscrutable rules.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I've suspected ever since I put the Ryzen system online, that the servers direct tasks specifically toward hosts with specific hardware. What you've observed on your own hosts does not surprise me at all. I think the servers run by their own inscrutable rules.

. . It certainly does seem that way ...

Stephen

:(

New thread started. Locking this thread at OP request.