1) the assimilator creates a job_summary_WUID file saying
- what host did the job
- error status if any
- info about missing output files
2) all output files are now optional.
3) the assimilator deletes temp files (templates, job dir file)
svn path=/trunk/boinc/; revision=15551
Otherwise, in compound apps we'll have both monitor and worker
reading the messages; this is a race condition
and will lead to spurious "no heartbeat" exits.
svn path=/trunk/boinc/; revision=15548
actions that deal with user rights and privileges and user
accounts.
- WINSETUP: Add some basic benchmarking code for user rights and
privileges
win_build/installerv2/redist/Windows/src/boinccas/
CACreateBOINCAccounts.cpp
CACreateBOINCGroups.cpp
CAGrantBOINCAdminsRights.cpp
CAGrantBOINCMasterRights.cpp
CAGrantBOINCProjectRights.cpp
CAGrantBOINCProjectsRights.cpp
CAGrantBOINCUsersRights.cpp
CAMigrateBOINCData.cpp
svn path=/trunk/boinc/; revision=15546
in scheduler request messages, without checking its contents.
One user had apparently edited global_prefs.xml with an XML editor;
it had an <?xml tag at the start,
and had been collapsed into a single line with no newlines,
and no newline at the end.
This caused all scheduler requests from that client to get
"Incomplete request" responses.
The long-term fix is for the client to verify global_prefs.xml,
and for the scheduler to parse it with XML_PARSER.
As a short-term fix, I made these changes:
- If the scheduler reads a line that's too long, it ignores it.
- The scheduler ignores <?xml
svn path=/trunk/boinc/; revision=15543
mostly so that the parse function could assume
that everything was initially zero.
However, various back-end functions pass around SCHED_CONFIG&
as an argument (also named "config").
This creates a shadow, which is always bad.
Worse is the possibility that some projects have back-end programs
that have a SCHED_CONFIG variable that's automatic,
and therefore isn't zero initially,
and therefore isn't parsing correctly.
To fix this, I changed the 2 vectors in SCHED_CONFIG into pointers,
and have the parse routine zero the structure.
I was tempted to remove the SCHED_CONFIG& args to back-end functions,
but this would have broken some projects' code.
I did, however, change the name from config to config_loc
to avoid shadowing.
Also fixed various other compiler warnings.
svn path=/trunk/boinc/; revision=15541
an automatic var SCHED_CONFIG (hence nonzero)
- make_project: include xadd in list of instructions
- boinc_submit: fix bugs in --stdin
svn path=/trunk/boinc/; revision=15536
set the timestamp of the thread to the timetamp of
the latest non-hidden post (rather than to now).
Same thing for forum timestamp.
- scheduler: return more informative message to user in case of
request message parse error
svn path=/trunk/boinc/; revision=15526
was being cast to a pointer to 64-bit time field
(this caused wrong results on 64-bit servers)
From Sharov Artyom.
svn path=/trunk/boinc/; revision=15517
This tells the sample bitwise validator to ignore this file.
- client: parse the above field (avoid "unparsed XML" msgs)
svn path=/trunk/boinc/; revision=15514
app executable from boinc_samples/example_app/uc2,
rather than boinc/apps/upper_case.
(boinc_samples must be installed in the same dir as boinc).
The reason: the BOINC autoconf-based build process
produces executables that have zillions of shared library dependencies,
and generally won't run on machines other than
the one where they were built.
Executables built in boinc_samples/ don't have this problem.
svn path=/trunk/boinc/; revision=15509
David Anderson