Message boards : Questions and problems : Files must be in home directory
Message board moderation
Author | Message |
---|---|
Send message Joined: 26 Jan 09 Posts: 29 ![]() |
I have Linux SuSE 11. I can't run BOINC unless I put the files in my user's home directory. ( /home/marathon for example) If I install to /home/marathon/BOINC or /home/marathon/Research/BOINC it won't work. If I open the BOINC manager, all the buttons except those under the statistics are disabled. There are no messages in the message window. The status at the bottom right says "disconnected." If, from the menu bar, I use tools --> attach to project, it is ignored. For now, I'll put the files in my user's home directory. I hope this will be fixed in a future version, and I will then be able to put the files in a sub-directory of my choosing. |
Send message Joined: 26 Jan 09 Posts: 29 ![]() |
That isn't it. The install program correctly set the contents of run_manager.sh Since it works for you, I suspect the problem is somewhere in permissions or security on my computer's setup. I recently upgraded to 6.4.5, and I have a new problem. When I shut down my computer, next time I start it, the project (Seti@Home) is lost! It is as if joining a project ant starting a work unit had not taken place. |
Send message Joined: 26 Jan 09 Posts: 29 ![]() |
Sorry about the delay. After installing it in my home directory, I had to wait for some work units to finish. Then, I got side tracked. In order to run the test you requested, I re-installed BOINC where I had it originally. It seems to work now, except SETI@home is offering no work units. More later ... |
Send message Joined: 26 Jan 09 Posts: 29 ![]() |
I got some work units, and it seems to be working. I can't recreate the problem. Interesting, because I had the same problem with previous editions of BOINC and SuSE. |
![]() ![]() Send message Joined: 30 Oct 05 Posts: 1239 ![]() |
It seems to work now, except SETI@home is offering no work units Seti doesn't always have work for the asking. If it's asking for work from Seti and it isn't getting it, it's a Seti problem, not a BOINC problem. Even if it's not asking for work from Seti, that doesn't necessarily make it a problem. The work scheduler is a complicated piece of software that I won't even pretend to understand. Kathryn :o) |
Send message Joined: 26 Jan 09 Posts: 29 ![]() |
Right. The fact that it was able to contact the server at SETI to find out that there was no work available suggested BOINC was working. Before, if I installed BOINC a sub-directory, it would not have contacted the server at all. I just wanted to let Dagorath know I hadn't forgotten about the test he asked me to do. Thanks for the help! |
Copyright © 2025 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.