| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Suggestions / Feedback
Thread: WUs cannot run on Linux x86_64 distributions with vsyscall=none |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I am currently using a self-built Linux LFS x86_64 distribution. When starting to compute WCG WUs, all of them throw computing errors, and the log of the system says "vsyscall attempt with vsyscall=none".
Our distribution aims at security so we disabled vsyscall since new glibc no longer needs it. All projects of WCG seem to be affected. Can WCG update these projects and avoid using vsyscall? |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
http://www.linuxfromscratch.org/lfs/view/development/prologue/architecture.html
The last paragraph... some sciences only come in 32 bit such as WCG's CEP2. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well, we do have a multilib-like solution - 32subsystem, which provides 32-bit libraries. This is not the point.
P.S. Now that some calculating programs is 32-bit, why can't BOINC detect it? Except for their responsibilities, I think WCG could try building 64-bit binaries, or post notifications for participants. |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Unless you tell the client to only ask for 64 bit, there's no mechanism to detect if a host is not 32 bit capable, but that was not my point.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I don't know if there has been any work on this issue, but Debian recently disabled vsyscall in testing. Currently it's impossible to run any WCG project at all.
|
||
|
|
|