Of course, I had no idea about your norm of "many". Just saw them there...
BTW: is there some (smaller) test WU available, such that a better comparison can be made. Not only useful for testing new apps, but also for changes in a computer (other OS and such)?
Up to August 11 stderr.txt was not empty, now it is on all results. Maybe the program has gone in vacation...Cheers.
Have you changed something at the BOINC Client side, e.g. upgraded it or attached to a new project then? It may also be that due to some change in permissions the Client is not able to store the stderr output of the App anymore.
Up to August 11 stderr.txt was not empty, now it is on all results. Maybe the program has gone in vacation...Cheers.
Have you changed something at the BOINC Client side, e.g. upgraded it or attached to a new project then? It may also be that due to some change in permissions the Client is not able to store the stderr output of the App anymore.
BM
Well, so far I was starting the 5.4.9 client first with "run_client" and then "run_manager". Then I read from the BOINC home page that the manager starts the client if it is not running and I started giving the "run_manager" command only. Maybe this is the reason. I shall go back to the old way and see what happens.
Tullio
For people who think the 4.16 runs faster on their machines than the 4.17 App I put a link to the 4.16 on our Power User Apps page. Note that this is the original Beta Test package, so if you intall the app_info.xml, all work already assigned to the 4.17 will end up with a client error.
For people who think the 4.16 runs faster on their machines than the 4.17 App I put a link to the 4.16 on our Power User Apps page. Note that this is the original Beta Test package, so if you intall the app_info.xml, all work already assigned to the 4.17 will end up with a client error.
BM
Thanks Bernd
I have a suspicion that this is the case on some but not all of my boxes, so now I will be able to run some tests, and confirm.
Well, so far I was starting the 5.4.9 client first with "run_client" and then "run_manager". Then I read from the BOINC home page that the manager starts the client if it is not running and I started giving the "run_manager" command only. Maybe this is the reason. I shall go back to the old way and see what happens.
Tullio
I confirm this guess. Starting the BOINC client first and the BOINC manager second gives back the stderr.txt text.
RE: However, quite some
)
Not so many. We have something like 50.000 templates in the long WUs, so less than 50 "small x" ist still < 0.1%. This result has 38.
BM
BM
Of course, I had no idea
)
Of course, I had no idea about your norm of "many". Just saw them there...
BTW: is there some (smaller) test WU available, such that a better comparison can be made. Not only useful for testing new apps, but also for changes in a computer (other OS and such)?
Regards,
Bert
Somnio ergo sum
On my latest result using
)
On my latest result using 4.16 (valid and pending) stderr.txt is empty. Why?
Tullio
RE: On my latest result
)
I am not sure why stderr.txt is empty but on my both linux machine is stderr.txt empty in all resluts.
Suse 10.1 Machine
live distro Slax 5.1.7
RE: stderr.txt empty in all
)
Up to August 11 stderr.txt was not empty, now it is on all results. Maybe the program has gone in vacation...Cheers.
Tullio
RE: Up to August 11
)
Have you changed something at the BOINC Client side, e.g. upgraded it or attached to a new project then? It may also be that due to some change in permissions the Client is not able to store the stderr output of the App anymore.
BM
BM
RE: RE: Up to August 11
)
Well, so far I was starting the 5.4.9 client first with "run_client" and then "run_manager". Then I read from the BOINC home page that the manager starts the client if it is not running and I started giving the "run_manager" command only. Maybe this is the reason. I shall go back to the old way and see what happens.
Tullio
For people who think the 4.16
)
For people who think the 4.16 runs faster on their machines than the 4.17 App I put a link to the 4.16 on our Power User Apps page. Note that this is the original Beta Test package, so if you intall the app_info.xml, all work already assigned to the 4.17 will end up with a client error.
BM
BM
RE: For people who think
)
Thanks Bernd
I have a suspicion that this is the case on some but not all of my boxes, so now I will be able to run some tests, and confirm.
RE: Well, so far I was
)
I confirm this guess. Starting the BOINC client first and the BOINC manager second gives back the stderr.txt text.