Charlie, More than one graphics application can be running at a time, hence why the graphics application log file ended up in the slot directory. Just creating a single user specific subdirectory isn't going to lead to a happy place.
It is supposed to be cleaned up when the slot directory is cleaned up. ----- Rom -----Original Message----- From: boinc_dev [mailto:[email protected]] On Behalf Of Charlie Fenton Sent: Wednesday, September 27, 2017 6:49 PM To: Charlie Fenton.SSL <[email protected]> Cc: boinc_dev email List <[email protected]> Subject: Re: [boinc_dev] Increase in errors on Windows clients related to shared memory On the Mac, the project graphics apps can not write to the per-user BOINC directory (which on the Mac is "/Users/{username}/Library/Application Support/BOINC/") because they run as user and group boinc_project under our UNIX account-based sandboxing. So I plan to set up a PR to create new per-user directories "/Library/Application Support/BOINC Data/users/" and "/Library/Application Support/BOINC Data/users/{username}/" with the same owner and group as the "/Library/Application Support/BOINC Data/projects/" directory, and write the stderrscrgfx.txt, stdoutscrgfx.txt, stderrgfx.txt and stdoutgfx.txt files there. I believe that a similar approach is probably needed for Windows, which has a simpler account-based sandboxing. But first I need to get my more urgent PR finished to fix the fact that the BOINC screensaver was broken by the recently released Mac OS 10.13 High Sierra. Cheers, --Charlie On Sep 27, 2017, at 2:51 PM, Charlie Fenton <[email protected]> wrote: > On Sep 27, 2017, at 12:49 PM, Juha Sointusalo <[email protected]> > wrote: >> I did see that the graphics app opens stderrgfx.txt file in slot >> directory and keeps it open as long as the graphics are open. > > That is not terribly useful, since it will be gone after the slot directory > is cleaned. It should go in the per-user directory, which on Windows is > C:/Users/{username}/AppData/Roaming/BOINC/ or at least in the project > directory. _______________________________________________ boinc_dev mailing list [email protected] https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
