resulting in many "finish file present too long" and 'exceeded time limit" errors.

Finish file errors can be resolved by moving to the 7.16.3 client. Exceeded time limit errors are likely caused by trying to support one too many cards on the bus.
You can find the latest Linux client at the BOINC ppa.
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc

Thanks for the heads-up. I had heard that 7.16.3 fixed the issue, but didn't know where to get it.
Unfortunately, I guess I'm still missing something, as after adding the PPA and issuing the update

sudo add-apt-repository ppa:costamagnagianfranco/boinc
sudo apt-get update

I'm still on 7.14.2 after a reboot.
Are there more steps required, considering I'm on the AIO so the installation is in /user/home/BOINC?
Thanks ...

---

No the installation from the ppa would be the standard repository location in /usr/bin/boinc-client. Just unpack the archive without running the installer and grab the BOINC client and manager files, boinc and boincmgr and drop them into your normal AIO /home BOINC directory.
Or to the immediate point just download the client and manager.
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc/+build/17833498/+files/boinc-client_7.16.3+dfsg+201910010804~ubuntu18.04.1_amd64.deb
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc/+build/17833498/+files/boinc-manager_7.16.3+dfsg+201910010804~ubuntu18.04.1_amd64.deb
Then just unpack them and not run the deb installer. The binaries are in the data package.

---

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

A proud member of the OFA (Old Farts Association)

No the installation from the ppa would be the standard repository location in /usr/bin/boinc-client. Just unpack the archive without running the installer and grab the BOINC client and manager files, boinc and boincmgr and drop them into your normal AIO /home BOINC directory.
Or to the immediate point just download the client and manager.
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc/+build/17833498/+files/boinc-client_7.16.3+dfsg+201910010804~ubuntu18.04.1_amd64.deb
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc/+build/17833498/+files/boinc-manager_7.16.3+dfsg+201910010804~ubuntu18.04.1_amd64.deb
Then just unpack them and not run the deb installer. The binaries are in the data package.

The downside to not using the package installer, I guess. Figured it was something like that. Again, thanks ...

---

Then just unpack them and not run the deb installer. The binaries are in the data package.

Guess I'll look at it later. Right now, it's making no sense, in that the extracted file sizes are vastly different.
Thanks, Bernie, for moving this thread! Much appreciated.

---

I checked the files. They report correctly. But the smaller sizes are likely because they weren't compiled with a debug library. Our AIO binaries were compiled with the debug symbols and are very large. If you strip out the debug symbols, the client binary is only about 1200KB instead of 20.1MB

Run

strip --strip-debug boinc

on your AIO binary and you can reduce the size also.

---

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

A proud member of the OFA (Old Farts Association)

I had the same observation about file sizes when I first started experimenting with the AIO and the spoofed client.

I think it would be better to disable or strip the debug symbols at the compilation stage, before distribution. That would save on download bandwidth, both for the downloader and the hosting site.

I had the same observation about file sizes when I first started experimenting with the AIO and the spoofed client.

I think it would be better to disable or strip the debug symbols at the compilation stage, before distribution. That would save on download bandwidth, both for the downloader and the hosting site.

True, that is if you don't need to debug established code. But since we are playing with the spoofed client, better to leave in for debugging purposes. Guess the code is settled now and we could make use of the --strip-all or -Wl parameter in the makefile and make a much smaller binary for reduced download bandwidth. Or for use on small SBC computers with limited RAM.

---

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

A proud member of the OFA (Old Farts Association)

Guess I can't get there from here ...

---

Can the AR be determined somehow from the file name like the ones below?

16jl09ab.22871.9065.7.34.215_1
blc61_2bit_guppi_58642_05986_HIP54072_0023.6488.0.21.44.69.vlar_0

kind of, but not precisely. (using the file name only, but can be determined by the WU header, see Richard's post below)

WUs without the "vlar" label will have AR values >(0.05-0.12)0.01 or so (I dont know the exact limit, but it's quite small), I've seen this go all the way up to like 180, but that's pretty rare.

WUs with the "vlar" label will then have AR values <(0.05-0.12)0.01

We refer to WUs that have AR >1 as "VHAR", but the project does not explicitly label them as such

---

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

.....Also want to get the _autosetup and configure to work. It is a real PITA to edit the Makefile. In addition want to look at a Windows version. I retired when my company switched platforms from Windows to Linux & CORBA. Linux was OK with me but I had exactly ZERO interest in CORBA.

Good luck with that. Petri and myself couldn't get it to work using _autosetup and configure.
The only way to see the Angle Range of the task is to either run the task, or open the task with a text editor and look at the <true_angle_range></true_angle_range> value.
The only correct way to test the different Apps is to run them in the Benchmark App using the same task for each App. Try running the CUDA 10.1 & 10.2 Apps in the Benchmark App using these WUs, http://www.arkayn.us/lunatics/Test_WUs.7z When I run that test I get different results, and the 10.2 results are better.

Can the AR be determined somehow from the file name like the ones below?

Apart from the crude vlar flag, NO.

But it can be determined from the plain-text XML header in the workunit data file:

<workunit_header>
  <name>blc14_2bit_guppi_58691_66098_HIP38931_0045.12140.818.21.44.27.vlar</name>
    <data_desc>
      <start_ra>7.9659866666667</start_ra>
      <start_dec>0.8143</start_dec>
      <end_ra>7.966</end_ra>
      <end_dec>0.8142</end_dec>
      <true_angle_range>0.014330391459691</true_angle_range>

- so a wider range than Ian&Steve said. I think the technical definition was "up to 0.05", but the practical line was drawn higher - at around 0.12

so a wider range than Ian&Steve said. I think the technical definition was "up to 0.05", but the practical line was drawn higher - at around 0.12

thanks for the clarification.

---

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

I have moved all the "off topic posts" to a new thread, if I missed any just red-x it and I will move it.

I also hid the discussion of how to get the job done as it had now been done and the posts were redundant ;-)

I have moved all the "off topic posts" to a new thread, if I missed any just red-x it and I will move it.

I also hid the discussion of how to get the job done as it had now been done and the posts were redundant ;-)

. . Thanks Bernie.

Stephen

I am a long-time Windows user. This thread is for someone who ALREADY knows some Linux, not a Linux noob.

I have several computers, and some are being considered for running Ubuntu and SETI. I have installed (that is, I followed the instructions)
Ubuntu 18.04.3 LTS on a thumb drive, then on an SSD, in a VM and also 19.10 in a VM. Trying to follow this topic here, about the 4th post
said to install something, and I am lost. I tried reading "The Complete Linux Manual Vol30 2019" on how to install other software, without
success. None of the instructions seem to work, so I need something quite a bit more elementary.

I tried to install BOINC using the instructions from the BOINC website but they didn't work. My installation didn't even recognize the command "APTITUDE".

Can someone point me to a very beginning level magazine or book, or set of instructions, on how to install software in Ubuntu? Baby step level.

I am not a fan boy for Windows, but I must give them credit for making life easy to load software.

what are you trying to install specifically?

for things that are in the standard repositories you would install with:

sudo apt install <package-name>

if it's not in the repos, you may have to add the repository that it's in.

sometimes if it's not available in any repo, you woul have to download a .deb file, or similar, and install it manually.

it really depends on what you are trying to do.

---

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

Like you, I set up a Linux box from scratch about 6 months ago. It's a steep learning curve, but my saviour was a Windows box alongside me as I worked, with Google* permanently open.

* other search engines are available.

I am running a SuSE Linux Virtual Machine on this Windows 8.1 PC with its 5.3.12 kernel. After starting it I download BOINC from SuSE and start it. The VM Linux PC is enlisted in Science United and gets tasks from it, mostly SETi. Milkyway and Asteroids. It cannot see the GTX 1050 Ti on the host PC and runs only CPU tasks on its A10-6700 CPU.
Tullio

---

I am running a SuSE Linux Virtual Machine on this Windows 8.1 PC with its 5.3.12 kernel. After starting it I download BOINC from SuSE and start it. The VM Linux PC is enlisted in Science United and gets tasks from it, mostly SETi. Milkyway and Asteroids. It cannot see the GTX 1050 Ti on the host PC and runs only CPU tasks on its A10-6700 CPU.
Tullio

I had the same problem with the "Windows Subsystem for Linux". It does not support OpenCL or CUDA.

I had the same problem with the "Windows Subsystem for Linux". It does not support OpenCL or CUDA.

It does actually now have the capability as WSL2 which was released this year uses a real virtualized kernel with device driver support rather than just translating all kernel system calls, but CUDA/OpenCL have yet to be implemented. Microsoft has indicated it's in development though I wouldn't expect it until perhaps mid-2020.

---