online scheduler logs. The only info that appears in these
online logs is then the HOSTID. If the user has chosen to hide
their hosts, then there is no way to figure out which user a
given hostid belongs to.
Note that this is exactly the same as the current approach of
displaying the results by hostid, but hiding the identity of the
user who owns a given host.
Also, increase default time for retaining logs to two weeks.
svn path=/trunk/boinc/; revision=9082
for users, helpers, and admins to view on the web.
A second script removes these log files if more than one week
old.
The logs are 'sanatized' by removing IP addresses and authenticators.
These scripts should be controlled by using the standard start/stop
scripts. To do this, make entries in config.xml. The files both
contain comments at the top detailing how to do this.
svn path=/trunk/boinc/; revision=9049
lib advertise data file when new result is created.
code organization: create new lib function boinc_touch_file()
from code that was in locality scheduler module.
svn path=/trunk/boinc/; revision=6456
config.xml. Use the boolean tag <cache_md5_info> to enable it.
This prevents the work generation library from having to go back and
continuously regenerate the md5 sums of your input data files. Note
that reading these from disk can be expensive if you have many such files
that are large and that you re-use. See check-in notes from 30/31 Dec 2004
for some details.
svn path=/trunk/boinc/; revision=5281
of gcc to try and force them to not complain with -Wall but to always
include this, I decided to take a simpler approach. All these strings
now have global linkage. To prevent namespace conflicts they all
have different names. For the record, the variable extension is a hash made of the first ten characters of the md5sum of the file path, eg:
md5hash=`boinc/api/x_opengl.C | md5sum | cut -c 1-10`
svn path=/trunk/boinc/; revision=4979
more recent than the 'md5info', then ignore md5info. If md5info
has *exactly* the right format (no extra or missing characters) then
remove it in this case (only). Don't write an md5info file if
another file is found with the same name. Thus if someone has two
data files called X and X.md5, unless X.md5 has the exact correct
syntax for an md5-info cache file, it won't be removed or used.
Still disabled by default. Use -DBOINC_CACHE_MD5 to enable it.
svn path=/trunk/boinc/; revision=4973
the cost of computing the md5 sums becomes expensive. Inserted
a simple caching mechanism into the utility function
process_wu_template(). For a given filename FILENAME, this looks
for a file called FILENAME.md5, which contains the md5sum and
length. If the file exists, these values are used. If not, such
a file is created. Since (I think) David is planning to have a
database for files, this mechanism will eventually be obsolete.
Right now it disabled by default. Use -DBOINC_CACHE_MD5 to
enable it.
svn path=/trunk/boinc/; revision=4965