| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Bonic stoped working |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 35
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
cd into the directory where you have installed BOINC then run ./boincmgr The 'run_manager' script that people have mentioned above simply does these steps for you (just take a look at the file). Make sure that BOINC is running first (via techniques discussed above) Obviously, since the manager is a GUI you need to be in an environment capable of displaying it (i.e. not logged in remotely). Well it never 'crashed' the system this time ... but, mucks@linux:~/BOINC/BOINC> ./boincmgr Gdk-WARNING **: Missing charsets in FontSet creation Gdk-WARNING **: JISX0208.1983-0 Gdk-WARNING **: KSC5601.1987-0 Gdk-WARNING **: GB2312.1980-0 Gdk-WARNING **: JISX0201.1976-0 connect: Operation now in progress init_poll: get_socket_error(): 111 ... and that is as far as I get.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well it never 'crashed' the system this time ... but, mucks@linux:~/BOINC/BOINC> ./boincmgr Gdk-WARNING **: Missing charsets in FontSet creation Gdk-WARNING **: JISX0208.1983-0 Gdk-WARNING **: KSC5601.1987-0 Gdk-WARNING **: GB2312.1980-0 Gdk-WARNING **: JISX0201.1976-0 connect: Operation now in progress init_poll: get_socket_error(): 111 ... and that is as far as I get. That's great. One of the errors 'init_poll: get_socket_error(): 111' is normal and then the GUI of the manager should come up. If it doesn't: 1. You use KDE or any other Window-Manager? You don't use the text mode console? 2. You did not change the user (using 'su') to run BOINC? If the user running the 'boincmgr' is different from the user who started the Window-Manager you might get problems during the connect. Try running 'xterm' instead of './boincmgr'. Do you get a new terminal? If not - something is wired with you instalation/setup in general. Just let us know how far you can get with the steps above. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thank you prause,
Yes I do get  the GUI of the manager, but again, when I close the 'shell' the manager then also closes. I can live with that, as long as it is "normal" ... I'll just use Desktop 2 I have what I need, I think, I thank you all for your time and patience in resolving this matter.  Sorry to have been a pain, but I really think Boinc for Linux "information" needs a little updating.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yes I do get the GUI of the manager, but again, when I close the 'shell' the manager then also closes. Sorry - got you wrong. If you wants the GUI to live longer than your shell you can start the manager like the core client: cd BOINC nohup boincmgr >& /dev/null & and you can close the shell w/o killing the GUI. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thank you once again ...
 |
|||
|
||||
|
|