On a new motherboard and O/S installation, yesterday I shared the BOINC data directory as BOINC so any program can refer to the BOINC data directory on any computer using UNC notation (i.e., \\ComputerName\BOINC) without knowing its actual location. That must have changed some permissions because after 8:50 on Jan 4, all the event log entries were written to stdoutTmp.txt and not to stdoutdae.txt, making it impossible to parse stdoutdae.txt for work unit start and finish times. Not a problem: a complete duplicate of stdoutdae.txt was in stdoutTmp.txt plus all the entries from Jan 4, 8:50 to Jan 5, 8:16. All I had to do was shut down BOINCMgr, take ownership of the BOINC data directory, rename stdoutTmp.txt to stdoutdae.txt, restart BOINCMgr, and all was fixed. Except that when I went to rename stdoutTmp.txt to stdoutdae.txt before restarting BOINC I found that they were identical in both length and content; all the log entries from Jan 4, 8:50 to Jan 5, 8:16 were gone. Why did BOINCMgr revert stdoutTmp.txt to the old stdoutdae.txt when I shut it down?
stdoutdae.txt is now updating correctly, except it contains no entries for the period Jan 4, 8:50 to Jan 5, 8:16. Does anyone know of any secret place these entries might be hiding? Charles Elliott _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
