Why is ...S5R6_1.01_graphics... a required file?
16 Oct 2017 18:27:55 UTC
Topic 210233
(moderation:
It's a Linux 64-bit system and typically running the O1SpotLo (AVX) application. I was doing routine system house-cleaning and noticed the <einstein_S5R6_1.01_graphics_i686-pc-linux-gnu> file present in the E@H directory. That file is a 32-bit executable, dynamically linked, and on my 64-bit system with no 32-bit libraries would never run; so I (foolishly) deleted it. After the running O1SpotLo app finished and the next cached work unit was started it terminated immediately (computation error - output file absent). And, in quick succession, all the remaining cache work units were "flushed out" in the same way. The good news is that BOINC/Einstein detected the missing file and downloaded it again. After that everything was back to normal.
Evidently that ..S5R6.. file is REQUIRED. My natural curiosity raises the question -- Why?
I also see a <einsteinbinary_BRP4_1.00_graphics_i686-pc-linux-gnu> file in the project directroy. It is also a 32-bit dynamically linked executable, which can never run. I guess I better leave it alone, too!
It will not come as a surprise that clicking on "Show Graphics" for a running E@H task in BoincMgr has no effect.
Curious only. Not a Bug. Not a Problem. (Now that I know what NOT to do.)
Indeed these executables are
)
Indeed these executables are meant to show the screensaver / starsphere graphics if they run. So we do ship these with the application. It is not an error (to the task or computing application) if these can't run. BOINC, however, has no notion of "optional" files for an application, it just checks if all files it considers as necessary are present, and errors out if not. In general, it's not a good idea to manually delete files that the BOINC client thinks it controls (unless you really know what you're doing), it will just get confused and may do weird things.
BM