Posts by whynot

21) Message boards : Questions and problems : How to control boinc with cron (linux?) (Message 62619)
Posted 20 Jun 2015 by whynot
Post:

Never did get cron to work, but I acquiesced and just ran my script in a timed loop in a tmux session, so I can kill the window and have it run in the background.


Surprise! Users have their private crontabs for decades. Refer to 'man crontab' for educational purpose.
22) Message boards : Projects : News on Project Outages (Message 62556)
Posted 13 Jun 2015 by whynot
Post:
Forum of ABC (if anyone remembers what it is) disallows login in. On BOINC side usuanl 'shut down for maintenance'. Is it finally dead or what?
23) Message boards : Questions and problems : Firewalls: Just what does BOINC want to talk to me? (Message 62193)
Posted 16 May 2015 by whynot
Post:

BOINC its parts talk to each other via remote procedure call, on localhost (127.0.0.1) only. They do this to be able to show in real time in BOINC Manager (the GUI) what the client is doing.


Correction. BOINC client *listens* on any network interface available on port 31416. That makes it possible to control/monitor BOINC *clients* with one BOINC *manager* over network. However, for standalone computer with alone client it's OK to allow listening/opening port 31416 on localhost (127.0.0.1) and forbidding on any other interface.
24) Message boards : Questions and problems : Install on CentOS 6.6 (Message 61677)
Posted 18 Apr 2015 by whynot
Post:
EDIT: I see now -- too late.
25) Message boards : Questions and problems : Migrating from old ".sh" BOINC to admin (YUM via EPEL) and service (Message 54631)
Posted 28 Jun 2014 by whynot
Post:
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.
26) Message boards : Questions and problems : Use HDD for BOINC work files instead of SSD (Message 53805)
Posted 26 Apr 2014 by whynot
Post:

CPU usage is about 1%, so boinc-client is not working on any tasks.


You don't judge by load. You look in logs.

Second, #8 provided then #5, #6, #7 are completely unnecessary.
27) Message boards : Questions and problems : NSA-Free projects ? (Message 52016)
Posted 18 Jan 2014 by whynot
Post:
*If* science code that's delivered to you is readable (note: there's no requirement that science code being free, it must be readable, that's all) then you can reasonably believe that someone already took a look. Thus you can reasonably believe that science code really does what is said it does. If actual science code is under wrapper then that wrapper should be readable too but that not required (you can see with your favored system monitor that wrapper isn't actually running all the time). Then, enlightened, you can reasonable conclude is it NSA-related or not just don't run under control of fantasies (remember, you're paying taxes, so, you know).

Otherwise, you can't.
28) Message boards : Questions and problems : BOINC manager doesn't connect in Fluxbox (Message 51828)
Posted 28 Dec 2013 by whynot
Post:
Couple of days ago I've assisted fellow cruncher who experienced that -155 too. I had to go thus I'm not aware how much successful he was. However, that's probably closest I've found.
29) Message boards : Questions and problems : Need tutorial - Linux console and BOINC (Message 51827)
Posted 28 Dec 2013 by whynot
Post:
Me would call this a "step-by-step". However, if you have difficulties pushing through some task please provide more specifics.
30) Message boards : News : New BOINC installer includes VirtualBox (Message 51727)
Posted 14 Dec 2013 by whynot
Post:

I won't actually care how slow the number crunching is if some programmer inadvertently or intentionally does something that I end up wishing she or he hadn't done.


There's that other solution for this problem. However, that solution is totally unwelcome, thus it's not going to happen.
31) Message boards : Questions and problems : I'm confused by the scheduling order. (Message 51609)
Posted 30 Nov 2013 by whynot
Post:

3) Somewhat less friendly, but will work is to just leave the settings alone and have some abandoned and late work when you get back from vacation. The science project will send replacements to someone else.


Don't abandon, that's not fair to project. Abort instead. For science sake, *don't be late*! There's a small percentage of crunchers who just hate to be overrun by late WU. Indeed, the percentage is small. But their hate is real and they are vocal. Abort instead.
32) Message boards : Questions and problems : I'm confused by the scheduling order. (Message 51480)
Posted 23 Nov 2013 by whynot
Post:

If you pause a single WU in the list, you will likely find a few surprises.


Better -- don't. That will make BOINC to ignore that unit at all. Technically speeking -- it would be out of buffer. Then BOINC might request more. Me suggests to set projects to 'nomorework' at appropriate time. It might be too late though.

2shawn Try to see another obstacle. The farer deadline, the longer WU. Indeed, you can't advice BOINC about upcoming vacation. Unless estimated times are borked and/or WUs have been suspended BOINC will finish all of them within deadlines. Ignoring upcoming vacation it doesn't know about.
33) Message boards : Questions and problems : redhat 6.4; latest boinc not compiling (Message 50906)
Posted 19 Oct 2013 by whynot
Post: 
3. ./configure --disable-{client/manager} --prefis=/usr/share/boinc


First, I believe it should be --disable-{client,manager} (probable typo). Second, I believe it should be --prefix= (sure typo). Third, I believe it's about building server-only parts of code, then.
34) Message boards : Questions and problems : Dual Boot... can I continue working on the same WU ? (Message 50066)
Posted 3 Aug 2013 by whynot
Post:
easy-peasy, partner :) I would suggest aproach it this way:



  • Make a partition that's dedicated to BOINC data directory. It doesn't have to be big, couple of GiB, I believe, should be enough. Filesystem should be carefully considered though. It should be either ext2 (you have to find way to mount it from win side; I suggest ext2fsd, from personal experience) or ntfs (go with ntfs-3g; shipped with kernel ntfs driver could be considered dead upstream, I believe). For gods sake, don't make it vfat -- vfat is brain-dead by design.

  • Install client outside of that BDD (BOINC data directory). For linux you can go with vendor shipped client (if any) or the client provided by BOINC itself. That choice is up to you.

  • Now you have to make sure that BDD is mounted before client starts. Obviously, it's influenced by choice you've made in first step.

  • Cross you fingers, pray, whatever, because,..



In spite of BOINC data directory is called 'data' it's not data exclusively.



  • There's code. And that code is for different platforms, you know. What if actual science code is placed under filename with no explicit platform?

  • BOINC wrappers are safe, however, you must feed BOINC with apropriate science application (and, may be, wrapper) before client sees unfinished WU.

  • Now you must do it each time a project needs to upgrade their science code.

  • Then, you *must* make sure that you report finished WU from the same platform you'd been scheduled for. (Again, from personal experience, there will be problems server side if those platforms mismatch, even slightly.)

  • Then, there are filenames in multiple configuration files under projects/ and slots/ trees. You have to handle problems if those filenames are not dealed with apropriately. (Why they should be? That could be handled with scripts though.)



Did I scared you enough? Is it really worth trouble?

35) Message boards : Questions and problems : Killed in terminal and the computation stops (Message 49538)
Posted 8 Jun 2013 by whynot
Post:
May I suggest you reading this tutorial (in spite of fancy name it looks relevant) and follow steps described? Probably you don't have problems with BOINC itself but with that optimus hardware or bumblebee software. And we here are no experts with either.
36) Message boards : Questions and problems : Ubuntu: BOINC takes 100% processor time ALL the time (Message 49194)
Posted 18 May 2013 by whynot
Post:
That's how "CPU share" works. What was your problem again?
37) Message boards : BOINC client : Client won't communicate after (removed) IP address conflict (Message 48833)
Posted 27 Apr 2013 by whynot
Post:
Yes, you can. You can put *your* computers (even if it's only one) behind your own router.
38) Message boards : Questions and problems : Suspend all Projects Command line? (Message 45433)
Posted 25 Aug 2012 by whynot
Post:
Guess what? Indeed it is:

	% boinccmd --get_project_status \
	  | sed -n -e '/master URL:/s/.\+URL://p' \
	  | while read ; do \
	    boinccmd --project $REPLY suspend \
	  ; done

39) Message boards : Questions and problems : BOINC processes keep crashing on excessive disk usage (Message 44673)
Posted 30 Jun 2012 by whynot
Post:
Only thing I could suggest would be to hemebrew a kind of a monitor what would watch for such disaster. However, the brewing itself should take place in more appropriate fora (whatever scripting language you prefer). I assume, that switching for less intolerant project is not an option.
40) Message boards : Questions and problems : boinc "box" with DCLinux (Message 42168)
Posted 21 Jan 2012 by whynot
Post:

It can boot from a USB floppy drive though so perhaps there is hope ?


Then you probably have an option. Difference between USB-HDD and USB-FDD could mean BIOS can't handle partition table on USB stick (what looks default configuration today). Your image must lend on USB stick starting with block #0. But I don't know the source, thus I can't say exact arguments for dd command to start reading the image from right block. Anyway, somewhere near the place you've got your live-image there could be instructions how to do it.


Previous 20 · Next 20

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.