Posts by Ifiguero

1) Message boards : BOINC client : Custom Windows Install (Message 39161)
Posted 21 Jul 2011 by Ifiguero
Post:
Thanks, I'll follow it from there.
2) Message boards : BOINC client : Custom Windows Install (Message 39153)
Posted 21 Jul 2011 by Ifiguero
Post:
I'm the sysadmin of 3 computer labs (about 120 computers, maybe more if I can add support from other admins).

I don't want that some users (because som apps require admin privileges) can access or modify boinc settings, so I can manage them remotely by BAM (run as service, no screensaver, only low mem/disc apps, run only if computer is unused).

With boinc 5.x I did this, now in 6.xx it seems that you cannot install only the client (at least in windows seems to be that way in linux there is no problem).

Is there any way to do this without building my own windows intaller?.
3) Message boards : BOINC client : Custom Windows Install (Message 39148)
Posted 20 Jul 2011 by Ifiguero
Post:
Is it posible to create a custom 6.xx install that silently install boinc client only.

It's for a massive deployment on shared PC that shouldn't manage what BOINC does (it's managed via BAM).

The idea it's to go with a thumbdrive and install the boinc-cmd quickly in a bunch of PC.

I read the wiki, but it seems that there is no way for installing only the client for windows, that why I'm asking here.

Regards
Israel

4) Message boards : Questions and problems : Account Manager "protocol" (Message 37637)
Posted 28 Apr 2011 by Ifiguero
Post:
I'm trying to implement "yet" another Boinc Account Manager (AM), I'm currently in a planning stage. I've been reading wikis, mailist, and the code of other similar project (jarifa) and there are some doubts for the correct management of the accounts/user/hosts.

First. if a host is attached to the AM using the weak autenticator. And after a while the user changues the password. How does it work? because the host no longer has the correct "weak" autenticator. I can only supose that the AM must update the account in the diferent projects and that they will provide the new weak autenticator to the host, so after a while the host will be able to reconect to the AM.

Second. If the host is attached to the AM using user/password. It's the same procedure?

The http://boinc.berkeley.edu/trac/wiki/AccountManagement is a bit misleading in this regard, because doesn't show this part of the process, or even the client contacting the project. It also imply that there must be allways a project atached when changing the password, or the whole scheme would fail and also that there are some race conditions where the node is ofline for a while and doesn't update properly unsyncing forever.

Another doubt is regarding that some AM user (IT managers) may want to set preferences or usage to a group of host (or farm) that has certain attribute (similar specs, geographic location, availability, owner). Setting to them some special preferences, projects to run, etc; but that doesn't seem compatible with the current boinc scheme. I mean, the more similar thing are the profile Venues, but they requiere that the host set the location, and it's limited to 3 diferent preferences. The only "solution" that I thought it's that the AM create multiple accounts in the project to satisfy the diferent preference requirements, but it will imply to create some kind of "email alias" to redirect all the account information to the same "real" user.

Any thoughts? I'm too wrong? Maybe someone can point me in the right direction (links are welcome).

Regards
Israel

PS: sorry about the bad english
5) Message boards : Projects : NQueens@Home (Message 19472)
Posted 13 Aug 2008 by Ifiguero
Post:
NQueens@Home Project successfully computed the number of solutions for the current world record which was the 25x25 board.

Now, it started to compute the number of solutions for the 26x26 board. And by this break the current WR.

Cheers




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.