Posts by cmosentine
| Info | Message |
|---|---|
| 1) Message boards : BOINC client : BOINC client / Virtualbox not respecting memory settings
Message 66550 Posted 31 Dec 2015 by  cmosentine
|
Have you checked what is taking up the memory? I have confirmed this is 100% an Atlas issue. Suspending Atlas instantly resolves the issue, re-enabling it causing the issue to promptly return. I wonder if VirtualBox is the culprit. I will be looking into downgrading VirtualBox to version 4.x, but I know opensuse will complain about it. I have also cross-posted this on the Atlas message board. |
| 2) Message boards : BOINC client : BOINC client / Virtualbox not respecting memory settings
Message 66549 Posted 31 Dec 2015 by cmosentine
|
I will check that out. |
| 3) Message boards : BOINC client : BOINC client / Virtualbox not respecting memory settings
Message 66524 Posted 30 Dec 2015 by cmosentine
|
Hi all: I have a fairly new linux box set up with opensuse leap 42.1 x64. I have BOINC 7.2.42 installed from the opensuse repositories. Virtual box is version 5.0.10. When I start the client I can watch the memory usage of my system steadily climb until over 98% of the available RAM is used. At that point my swap file starts getting hit hard and my system will slowly become less responsive to the point of no response. If I stop the BOINC client memory usage drops back to about 10%. I can repeat this behavior at will. Suspending ATLAS and VLHC projects alleviates the issue somewhat but memory usage still go to about 55%. I had my initial memory usage setting fairly aggressive, 75% while in use and 90% while the system was idle. As a test I set both to 25% so that whether or not the system was in use or idle only 25% RAM should get used. But this has no effect on memory usage. Any ideas how I can get memory usage under control???? Thanks Chris. My system consist of the following: AMD FX-8350 CPU 8 GB RAM 500 GB HD Nvidia Geforce 950 GT video card. OpeneSuse Leap 42.1 X64 - fully patched |
| 4) Message boards : BOINC Manager : installing only the Manager on OSX
Message 66495 Posted 29 Dec 2015 by cmosentine
|
Why not install BOINC completely and when running it, not add any projects? Thanks for the reply. That is what I am doing right now but it is messy as the client always starts when the manager starts. No need to have extraneous processes running. |
| 5) Message boards : BOINC Manager : installing only the Manager on OSX
Message 66492 Posted 29 Dec 2015 by cmosentine
|
I want to install the BOINC Manager only on my Macbook Pro so that I can use it to administer my other BOINC Client machines. I have the full BOINC package installed but have not configured the client to do any work as I don't want to do crunching on my laptop. So far I can't seem to make this work by coping the manager application, removing BOINC, and then starting the manager from the copy. I know it was a long shot. I see there are instructions to build the manager from source on github, but I would rather find a pre-compiled manager-only package. Has anyone successfully installed/built/run the BOINC manager only?? How? |
| 6) Message boards : Questions and problems : openSUSE 12.1 + BOINC = failure
Message 42281 Posted 27 Jan 2012 by cmosentine
|
Oh come one, just a little ribbing. |
| 7) Message boards : Questions and problems : openSUSE 12.1 + BOINC = failure
Message 42274 Posted 27 Jan 2012 by cmosentine
|
Thanks for the reply. I understand the issues involved with maintaining working software across all the linux distro's out there. The idea of a symlink sounds like a plan. PS. I like your avatar but it would look better with B.O.'s face :P |
| 8) Message boards : Questions and problems : openSUSE 12.1 + BOINC = failure
Message 42261 Posted 26 Jan 2012 by cmosentine
|
Hi all: I am getting a bit frustrated trying to get BOINC running on my freshly installed opensuse 12.1 box. I have tried to get things running two different ways, with each met with failure. 1. I installed BOINC client and manager via the opensuse repositories. There is a bug in the repository install involving a missed-named file (for launching the manager gui) which I fixed. However, I cannot successfully launch the client as it returns an error stating it needs to be initialized. That's fine but I can't initialize it via the manager without the client running. Does anyone have a proven recipe to get BOINC running via the repository install? 2. I have also tried installing via the latest installer from BOINC. Installer runs fine and I can get the boinc-client running without issue. However, I cannot get the manager to run to a library mismatch with opensuse 12.1 (needs libnotify1 but opensuse provides libnotify4). So, does anyone have a suggestion on how to get this install method working? Thanks, Chris. |
| 9) Message boards : BOINC client : OSX client and unnamed user accounts
Message 41564 Posted 10 Dec 2011 by cmosentine
|
Thanks for pointing that out, but is this not a bit of security through obscurity? It's my computer, I can enable root and gain access to this data, and so could anyone else on my computer with admin rights. Unless the BOINC client breaks some basic unix security, I don't see the need. |
| 10) Message boards : BOINC client : OSX client and unnamed user accounts
Message 41549 Posted 10 Dec 2011 by cmosentine
|
Hi all: I am new to te OSX client and have noticed that the installer creates two unnamed user accounts which are given smb sharing privileges. This seems rather odd to me that they would be unnamed. I have confirmed they are created by the BOINC installer. Is this normal behavior? Can the accounts be altered to give them names? I don't consider this terribly good form. Tanks, Chris. |
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.