Hi,

We have done a search on Event log file location and nothing came up hence why we post this question.

Can someone tell us where the information presented in:

Tools | Event Log

Is actually stored, and if it is within a file, or some other persistent storage?

We want to write some software that analyses Work Units (WU) that have been downloaded and reported with 24 hours, and this would seem the best way to do this as it contains the necessary information within the Event Log.

Obviously we would be mindful of the file being possibly locked due to the BOINC client reading/writing into it.

Thanks.

It's being logged to the stdoutdae.txt file, which is in the BOINC data directory. Where that is depends on your operating system.

---

Thank you Ageless, its much appreciated.

Would it be possible to make a suggestion?

Could I suggest that this file be written out as a CSV file? If would be a lot easier to read in code if the file were.

The reason I ask is because if you try and import this file it basically breaks the whole file apart and makes it unusable, as it gets confused between the space used as a delimiter within the first 2 elements, and then the later spaces within the description; eg uploaded XXXXX etc.

Thanks

Could I suggest that this file be written out as a CSV file? If would be a lot easier to read in code if the file were.

The output file writes to a generic text file, as this is compatible between all the platforms BOINC is built for. Also, when enabling debug flags, it would be nice to be able to read the debug output in a coherent way, instead of having commas between every word. There are however plenty of possibilities to convert a text file to comma separated values.

There are also already a lot of third party add-ons that use the present output files, so to go change the output manner for a new setup would break it for all the old ones, that wouldn't be a nice thing to do.

---

Perhaps you might get better information about tasks if you look at

a) job_log_<project_name>.txt file in the boinc data directory, which records all completed tasks.
b) or use the various boinccmd command options such as

--get_tasks # show tasks
--get_old_tasks # show reported tasks from last 24 hours

Event logs are quite dynamic, easily overwritten and liable to be tuned by user settings.

Thank you Agentb, that is very useful.

Sorry I have only just seen this post.