Migrating from old ".sh" BOINC to admin (YUM via EPEL) and service

Message boards : Questions and problems : Migrating from old ".sh" BOINC to admin (YUM via EPEL) and service
Message board moderation

To post messages, you must log in.

AuthorMessage
DaniM

Send message
Joined: 25 Jun 14
Posts: 1
Spain
Message 54589 - Posted: 25 Jun 2014, 9:33:44 UTC

Hi,

I'm running CentOS 6.5 64bits.

I've been running BOINC for years, installing it locally (running the .sh script in a directory, with the configuration and logs saved there).

After some system updates, BOINC (old 6.x version) stopped working. Trying to update to BOINC 7 I discovered that (due to library version incompatibility, etc) I could better install it via YUM (using EPEL repositories). Now It's installed and working, but It doesn't read my "old" configuration files.

Is there any "easy way" to tell BOINC "take my old configuration files from /home/myuser/BOINC/"?

I cannot spend more time on it, and I'd like to continue running BOINC on this computer.
ID: 54589 · Report as offensive
whynot

Send message
Joined: 8 May 10
Posts: 89
Ukraine
Message 54631 - Posted: 28 Jun 2014, 14:25:53 UTC

Loads of. Move files in directory where client looks for them (permissions/ownership changes provided); client has '--dir' option; symlink files (probably worst case). I would recommend: disable system-wide client, create symlink legacy-boinc-data-dir/boinc-client (or whatever it was) to system-installed client (probably /usr/bin/boinc-client, it's debian here), and ignite it the way you did for years.
I'm counting for science,
points just make me sick.
ID: 54631 · Report as offensive

Message boards : Questions and problems : Migrating from old ".sh" BOINC to admin (YUM via EPEL) and service

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.