Open RyokoAsakura opened 2 years ago
I don't seem to be having this issue, can you confirm you are still getting this problem @RyokoAsakura?
I can confirm that I am still having this issue. So much, in fact, that I still have a script cron'ing a file copy from the folder every 2 minutes.
Have you pulled the latest updates? I'm not having this issue so maybe you're still on a old build?
Just pulled, now running latest update (865e5c7) and the problem still exists.
Can you share your goesproc conf file so I can compare to mine.
Just compared uses to mine and the only thing I see that's diffrent is theres a "." in my path at the start. Maybe try doing that as well?
[[handler]]
type = "emwin"
directory = "./emwin/{time:%Y-%m-%d}"
exclude_txt = true
No change. All that does is tell it to use the current directory.
I'm not sure what else to try, it's working fine for me and my friend who also uses my goesrecv stream. Hopefully someone else can come forward and assist, sorry I could not be of help.
I appreciate your effort. Thanks!
Personal solution until it gets fixed:
I have written 2 scripts that moves the 1969-12-31 in EMWIN to the proper place. The one script is for the current UTC day, and the second script is for whenever your local day is after UTC 00:00. I run them via cron job every 2 minutes during appropriate hours. The only thing you have to do is adjust the hours they get run based on when your local time is UTC 00:00.
Here's my cron layout for UTC+5 (US Eastern Time) /2 0-19/1 bash /home/pi/move1969.sh /2 20-23/1 bash /home/pi/nextdaymove1969.sh
And attached are the bash scripts for both. Hope these can help. Don't forget to remove the .txt and also to chmod +x the scripts before you set the cron job for them.
--Ryoko
It would appear that I am having the same problem in my EMWIN folder/date creation as was occurring for nws in issue #100. Is there any way to fix the emwin handler so this doesn't happen?
Thank you in advance.