Aloha,
[...]
Also event_manger.log is made up entirely of:
[2017-02-09 00:22:08.242] [info ] [burger ] [ 3996: 4000] Storage path was not set so neither stored FFL key nor stored events are read.
[2017-02-09 00:22:08.258] [info ] [burger ] [ 3996: 4784] Storage path was not set so loading of stored events is skipped.
[2017-02-09 00:22:08.820] [info ] [burger ] [ 3996: 4784] Storage path is not set so storing of FFL key is skipped.
[...]
I'm also wondering about that.
Thanks for your collective thoughts.
I have the same thing dating all the way back to 2016-04-10
There was a debugging entry in the logfile that displayed some hardware info. That extra info was included until 2016-07-01 at which time the hardware info ceased getting written into the logfile. Was an update from AVast installed around then???
Since there are just a few files that trigger this event (in my case, I'd be more than happy
to find the offenders, clean them up, and go on my merry way if I only knew why and how). Hoping to see some action on this from AVast Tech Support
. It generally appears benign, but you never really know unless a technically knowledgeable person does the evaluation.