How to autostart boinc?


log in

Advanced search

Message boards : Number crunching : How to autostart boinc?

Author Message
Profile Dentaku
Avatar
Send message
Joined: 24 May 99
Posts: 26
Credit: 63,136
RAC: 96
Germany
Message 2095 - Posted: 25 Jun 2004, 20:06:25 UTC

I tried to create a symbolic link into my ~/.kde/Autostart/ folder but when i retsart the computer, boinc doesn't start. I also tried to create a script:

#!/bin/bash
~/Programme/BOINC/boinc_3.18_i686-pc-linux-gnu &

in the Autostart folder and made it executable (chmod +x) but this also doesn't do anything.

Then i started this bash script in a shell manually and the following apperas:

2004-06-25 22:04:58 [---] Starting BOINC client version 3.18 for i686-pc-linux-gnu
Enter the URL of the project: You should have already registered with the project
and received an account key by email.
Paste the account key here: 2004-06-25 22:04:58 [---] Renaming account_.xml to account.xml
boinc_3.18_i686-pc-linux-gnu: cs_account.C:37: std::string filename_to_project_dirname(const std::string&): Assertion `starts_with(filename, "account_")' failed.
SIGABRT: abort called
Exiting...


of course, i already have an account and also started boinc successfully by hand. if i start it directly, it works.

???

wedgenix
Send message
Joined: 3 Apr 99
Posts: 19
Credit: 0
RAC: 0
Message 2104 - Posted: 25 Jun 2004, 20:21:34 UTC - in response to Message 2095.

Don't restart ;)

JoseCanUC
Send message
Joined: 27 Apr 03
Posts: 6
Credit: 355,235
RAC: 0
United States
Message 2115 - Posted: 25 Jun 2004, 20:31:14 UTC

Just a wild guess, but have you tried having your shell script change the current working directory to the one holding the Boinc client?
Example:

#!/bin/bash
cd ~/Programme/BOINC
./boinc_3.18_i686-pc-linux-gnu &

CXI
Send message
Joined: 23 Apr 99
Posts: 30
Credit: 270,498
RAC: 0
United States
Message 2116 - Posted: 25 Jun 2004, 20:31:29 UTC
Last modified: 25 Jun 2004, 20:40:55 UTC

Try this:

#!/bin/bash
cd ~/Programme/BOINC
./boinc_3.18_i686-pc-linux-gnu &

It looks like it can't find the information files which tell it what projects to connect to because the autostart is running it from some other directory.

Heh, JoseCanUC you beat me by just a few seconds. :) Another suggestion, I use a program called screen to keep the client active, instead of running it in the background. I did the same with the old seti. Screen allows you to disconnect from the screen session and leave it running after you log out. When you log back in, screen -r reconnects you to the session and it's like you never disconnected. It keeps a scrollback buffer as well. In addition, screen supports multiple terminals within one screen, allowing you to go do other things and switch back and forth between the terminals with a keystroke. Of course, the new client doesn't have a verbose mode like the old one did, but you can see the errors. :)

Profile Dentaku
Avatar
Send message
Joined: 24 May 99
Posts: 26
Credit: 63,136
RAC: 96
Germany
Message 2155 - Posted: 25 Jun 2004, 22:52:18 UTC - in response to Message 2115.

> Just a wild guess, but have you tried having your shell script change the
> current working directory to the one holding the Boinc client?
> Example:
>
> #!/bin/bash
> cd ~/Programme/BOINC
> ./boinc_3.18_i686-pc-linux-gnu &

Yup! That's the trick! Thanks! :-)

Message boards : Number crunching : How to autostart boinc?

Copyright © 2014 University of California