Paola is soon sending a comonly-sized one (for LONG), aimed at ~10h on GTX580s and upload file sizes of ~80Mb. As compensation, we are adding an extra 5% credit on the new ones.

Additionally, we are looking at ways to reduce the size of uploads for the users, thought it is not clear at this point if we will be able to do that. Please be patient with the implementation of changes/improvements.

Actually, I got that advice from you in another thread. Solved the problem I had earlier.

Hi, What I can say is that in Ubuntu 10.10, / etc / environment, it works perfectly. Greetings.

Well, where did you put the swan_sync environment variable? Different distros read the environment variable in different places, so YMMV.

EDIT: For instance, I placed the line "export SWAN_SYNC=0" in my /etc/default/boinc-client file (Linux Mint 10). Others have reported that placing it in /etc/environment works, but it didn't work for me.

/etc/default/boinc-client

/etc/sysconfig/boinc-client

# Enable SWAN_SYNC for GPUGRID project
export SWAN_SYNC=0

For anyone getting started with GPUGRID on Fedora here's how you can set it up. It may also work for other RPM based distros.

1. To install BOINC, run the following command as root:

yum install boinc-client boinc-manager

2. To improve GPUGRID performance you can dedicate a CPU core to the GPUGRID app. To do this enable swan_sync by adding the following to /etc/sysconfig/boinc-client:

# Enable SWAN_SYNC for GPUGRID project
export SWAN_SYNC=0

3. Reboot.

4. Run the BOINC Manager (in the System Tools menu). Check the messages to verify that your GPU was recognized. If everything looks good attach to the project and begin crunching.

However I'm pretty sure readenv=1 is the PAM default (readenv=1 tells pam_env.so to read /etc/environment).

Lacking any readenv=0, I do not understand why your /etc/environment isn't read. I may be wrong about the default PAM behaviour, of course.
I'll try a little bit harder.

Bye, and thank you again. :)

I've just tried on a live virtualized fedora 14, and /etc/environment is actually read.
I don't know why on your system it is not. Sorry, I have to give it up.

Bye.

sudo chkconfig --level 1234 boinc-client off

All runlevels? So even at S (single user from boot, 1 in Fedora)? This is clearly wrong, and is the cause of the "GPU not recognized" problem.
In Ubuntu I start it at 2345 and stop it at 601.
In Fedora I'd suggest to start it just at 5.

Bye.

Add the line,

<start_delay>30</start_delay>

to the cc_config.xml file (or create the cc_config.xml file and add the line if you have to).

A possible alternative for some Fedora systems with network driver not loading fast enough (but might also work here, as it forces a delay).

Add the line NETWORKWAIT=yes to /etc/sysconfig/network to delay system startup for 10 seconds or until a network connection is up.

From http://boinc.berkeley.edu/wiki/Network_related_problems

With Ubuntu I solved changing the /etc/init.d/boinc-client starting prefix to 98.

# update-rc.d -f boinc-client remove
# update-rc.d boinc-client defaults 98 02

I don't know which is the proper command for Fedora, though.

Bye.

# chkconfig: - 98 02

chkconfig boinc-client resetpriorities

echo "service boinc-client restart" | at now + 1 minutes

Your solution works flawlessly. Well done!

Since I don't know Fedora, could you please help me understand? I suspect that Fedora's PAM configuration is slightly different with respect to Ubuntu's one. I guess that running:

$ grep "pam_env.so" /etc/pam.d

you'll get some output containing "readenv=0". Is it true?

Thanks.
Bye.

yum install boinc-client boinc-manager

export SWAN_SYNC=0

     export SWAN_SYNC=0