*** empty log message ***

svn path=/trunk/boinc/; revision=11257
This commit is contained in:
David Anderson 2006-10-09 17:02:37 +00:00
parent a3afccb8c2
commit e00ee5c5da
8 changed files with 41 additions and 14 deletions

View File

@ -10922,3 +10922,10 @@ David 6 Oct 2006
client/
cs_prefs.C
David 9 Oct 2006
- core client: when parsing list of project files in sched reply,
delete the old sym link files first
client/
client_types.C

View File

@ -452,7 +452,21 @@ void PROJECT::file_xfer_succeeded(const bool is_upload) {
int PROJECT::parse_project_files(MIOFILE& in) {
char buf[256];
unsigned int i;
char project_dir[256], path[256];
// delete current sym links.
// This ensures that we get rid of sym links for
// project files no longer in use
//
get_project_dir(this, project_dir);
for (i=0; i<project_files.size(); i++) {
FILE_REF& fref = project_files[i];
sprintf(path, "%s/%s", project_dir, fref.open_name);
boinc_delete_file(path);
}
project_files.clear();
while (in.fgets(buf, 256)) {
if (match_tag(buf, "</project_files>")) return 0;
@ -471,6 +485,9 @@ int PROJECT::parse_project_files(MIOFILE& in) {
return ERR_XML_PARSE;
}
// install pointers from FILE_REFs to FILE_INFOs for project files,
// and flag FILE_INFOs as being project files
//
void PROJECT::link_project_files() {
vector<FILE_REF>::iterator fref_iter;
fref_iter = project_files.begin();

View File

@ -40,7 +40,7 @@ automatically when selected users log in, see the <a href=mac_admin_tools.php>Ma
<p>
If you install the command-line client and want it to start automatically when each user logs in, see the
<a href=mac_yenigun.php>Instructions from Berki Yenigun</a>,
<a mailto=stegozor@gmail.com?Subject=Boinc_automatic_startup>stegozor@gmail.com</a>.
<a href=mailto:stegozor@gmail.com?Subject=Boinc_automatic_startup>stegozor@gmail.com</a>.
";
page_tail();

View File

@ -6,7 +6,7 @@ array("October 4, 2006",
by Mike O'Connell of BOINC UK.
Many topics were covered, including the question of
credit and optimized clients.
Download an recording of the conversation (MP3, 13.5 MB) from
Download a recording of the conversation (MP3, 13.5 MB) from
<a href=http://www.boincuk.com/david_anderson.mp3>BOINC UK</a>
or <a href=mp3/boincuk_4_oct_2006.mp3>a mirror at Berkeley</a>."
),

View File

@ -77,7 +77,7 @@ Each area is managed by an 'owner'.
</tr>
<tr>
<td>Web features</td>
<td>David Anderson</td>
<td>Rytis Slatkevicius</td>
<td><a href=http://rob.axpr.net/>Rob Ogilvie</a></td>
</tr>
<tr>

View File

@ -62,8 +62,7 @@ array(
),
array(
"<a href=http://www.pperry.f2s.com/downloads.htm>SETI-Linux</a>",
"Linux i686, linux athlon xp, Linux AMD64,
Linux Pentium 3. Some Links to other Platforms",
"Linux: i686, Athlon-XP, AMD64, Pentium 3. Some Links to other Platforms",
"BOINC, SETI@home"
),
array(
@ -89,13 +88,14 @@ array(
),
array(
"<a href=http://www.lb.shuttle.de/apastron/boincDown.shtml>Stefan Urbat</a>",
"Solaris: SPARC, AMD64 (Opteron) and x86
<br> GNU/Linux: AMD64 (Opteron), PowerPC, Itanium, s390
<br> HP-UX (PA RISC and Itanium/IA64)
"Solaris: SPARC, AMD64 (Opteron), x86, i686
<br> Linux: Alpha, SPARC, AMD64 (Opteron), PowerPC, Itanium, s390
<br> HP-UX: PA RISC and Itanium/IA64 (includes BOINC Manager)
<br> Tru64: Alpha
<br> AIX: Power4 and later
<br> OpenBSD: x86
<br> NetBSD: x86
<br> FreeBSD: x86, Alpha
",
"BOINC core client, SETI@home"
),

View File

@ -4,12 +4,12 @@ require_once("docutil.php");
page_head("Preferences override file");
echo "
By default, <a href=prefs.php>global preferences</a>
are maintained on a project server,
and host venue are maintained on a project server,
edited via a web interface, and downloaded from the server.
<p>
Some people may want to edit preferences locally,
or modify preferences on a single host.
modify preferences on a single host, or hardwire the host venue.
To accommodate these requirements, BOINC lets you
create a 'preferences override file'.
This file is read by the core client after
@ -23,9 +23,9 @@ Its structure as follows:
<run_on_batteries>0</run_on_batteries>
<run_if_user_active>0</run_if_user_active>
<start_hour>0</start_hour>
<start_hour>0</start_hour>
<net_start_hour>0</net_start_hour>
<end_hour>0</end_hour>
<net_start_hour>0</net_start_hour>
<net_end_hour>0</net_end_hour>
<leave_apps_in_memory>0</leave_apps_in_memory>
<confirm_before_connecting>0</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
@ -42,6 +42,7 @@ Its structure as follows:
<max_bytes_sec_up>0</max_bytes_sec_up>
<cpu_usage_limit>100</cpu_usage_limit>
</global_preferences>
[ <host_venue>venue</host_venue> ]
")."
<p>

View File

@ -6,7 +6,6 @@ echo "
<p>
Participants in a project can form <b>teams</b>.
Each participant can belong to at most one team.
The participant who created the team is called its <b>founder</b>.
<p>
A team is local to a project.
There is currently no provision for teams that span projects.
@ -24,7 +23,10 @@ A team has the following attributes:
<li> A textual description.
<li> An optional URL (e.g., of the team's web site)
<li> A type (business, school, club, etc.).
<li> The founder.
<li> The <b>founder</b>: initially, this is the user who
created the team, but it may change (see below).
A team's founder may quit the team,
but will remain as its founder.
<li> A list of members.
</ul>