I don't think so. DS_Store is just used by Finder for custom folder display options.
What do you get when you try the log command I posted, immediately after running weewx? Are you running weewx directly from the command line? What happens if you try the utility wee_reports <http://weewx.com/docs/utilities.htm#wee_reports_utility>? -tk On Mon, Apr 17, 2017 at 2:32 PM, MRL <[email protected]> wrote: > Seems to be an access violation. Not sure how to fix this. > > Violation: System Policy: deny file-write-create > /System/Library/Frameworks/Python.framework/Versions/2.7/ > Resources/.DS_Store > MetaData: {"build":"Mac OS X 10.12.4 (16E195)","action":"deny"," > target":["System","Library","Frameworks","Python.framework" > ,"Versions","2.7","Resources",".DS_Store"],"hardware":"Mac", > "platform_binary":"yes","profile":"unknown","process":" > Finder","op":"file-write-create"} > 2017-04-16 19:49:54.266202-0400 0x4f26d Error 0x0 > 163 sandboxd: [com.apple.sandbox.reporting.violation] > SandboxViolation: Finder(312) System Policy: deny file-write-create > /System/Library/Frameworks/Python.framework/Versions/2.7/Resources/.DS_Store > [Duplicate; no report will be generated.] > 2017-04-16 19:50:22.983233-0400 0x4f3ac Default 0x0 > 0 kernel: (Sandbox) SandboxViolation: Finder(312) System Policy: > deny(1) file-write-create /System/Library/Frameworks/ > Python.framework/Versions/2.7/.DS_Store > 2017-04-16 19:50:22.983262-0400 0x4f3ac Default 0x0 > 0 kernel: (Sandbox) SandboxViolation: Finder(312) System Policy: > deny(1) file-write-create /System/Library/Frameworks/ > Python.framework/Versions/2.7/.DS_Store > 2017-04-16 19:51:27.277776-0400 0x4f2a5 Error 0x0 > 163 sandboxd: [com.apple.sandbox.reporting.violation] > SandboxViolation: Finder(312) System Policy: deny file-write-create > /System/Library/Frameworks/Python.framework/Versions/2.7/.DS_Store > On Monday, April 17, 2017 at 4:15:53 PM UTC-4, Tom Keffer wrote: >> >> Hard to say without seeing the log, which brings us to a deep flaw with >> Sierra: they changed the logging facility in such a way to make it >> extremely difficult to access it. >> >> There is still the file /var/log/system.log, but it will only contain >> events with very high priority. To see the lower level events that weewx >> generates, you have to use their "unified logging" facility, which is >> extremely difficult to use. This kind of works for me: >> >> 1. Run weewx >> 2. Now check the log for the last few minutes, grepping for just the >> Python stuff: >> >> *log show --info --debug --last 3m | grep Python* >> >> >> There may be an easier way to do this, but it's the best I can come up >> with. Even so, it will only show the Python-related logging events, so you >> may miss some OS-related events that are relevant to your problem. >> >> Help from any Mac expert would be eagerly welcome! >> >> -tk >> >> >> On Mon, Apr 17, 2017 at 12:35 PM, MRL <[email protected]> wrote: >> >>> My thanks for the quick responses to get weeWX running on my Mac - the >>> change to setup.cfg did the trick. >>> Started the program and it is getting data from the Davis Vantage Pro/2. >>> Tons of png files in the public_html directory but no index.html >>> It has been about 30 minutes since the program started. >>> Program is continuing to read data - look OK. >>> >>> What happened to index.html? >>> Thanks again >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "weewx-user" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "weewx-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
