Logging
OS: Win10
Logos 7
Documents is not a proper location for logs and I can find no method by which to change the Logos Log Files location. I've added the Enabled=0 registry entry but that only disables cef.log, not error logs, PBB logs, etc.
The issues this causes deals with using OneDrive as the default save location for documents, causing conflicts and rendering the log files useless since I don't know which machine's logs are which since they all sync/overwrite (I have a desktop, laptop, and a Surface, all in sync).
Reconfiguring OneDrive isn't an option (excluding one folder means I have to manually add new ones, introducing the potential for human error).
How can I change the Logos log file location? Failing that, how do I disable all logging entirely?
If there aren't answers to either of these questions, then my request would be to add a means to specify the log location or, better still, just have it in AppData where it belongs and add a link in the Start menu to its location.
Logos 7 Base + Platinum Library + Now | Surface Pro 2017 | i7-7700K Desktop | i7-4800MQ Gaming Laptop | Android 7.1.2
Comments
-
Julian West said:
How can I change the Logos log file location?
The location can't be changed,and you can't prevent certain log files being generated as information about errors and crashes are important.
As it appears that OneDrive can't easily be changed, try to redirect Logos Log Files to another folder e.g. to \AppData in each of your computers.
Dave
===Windows 11 & Android 13
0 -
Redirecting is moot since OneDrive will still sync the redirected folder. This is how one syncs folders that are outside of OneDrive's tree.
I managed to stop the cef.log from updating by making it Read-Only and Hidden.
Logos 7 Base + Platinum Library + Now | Surface Pro 2017 | i7-7700K Desktop | i7-4800MQ Gaming Laptop | Android 7.1.2
0 -
There is no way to completely disable logging; some log files are always written.
We know that Documents is the "wrong" place to save log files (they're not user-created documents) and have recently been discussing this problem internally. I've added a link to this post (with the problems it's causing for OneDrive) to that discussion.
0 -
Thanks! That would be great.
Rather than create another thread, I'd like to add another niggle: I don't need to be notified every single time Logos is indexing. Logos is good about mentioning it when its relevant: when I'm searching the library. It also places an icon in the systray. After the first time, the notification is unnecessary.
I can't find a way within Logos to disable this; I had to disable all notifications from Logos in Windows settings (are there any other notifications besides that one?).
Logos 7 Base + Platinum Library + Now | Surface Pro 2017 | i7-7700K Desktop | i7-4800MQ Gaming Laptop | Android 7.1.2
0 -
Julian West said:
I managed to stop the cef.log from updating by making it Read-Only and Hidden.
Perhaps you can do that for the other ones e.g. Logos.log, LogosIndexer.log, LogosError.log, LogosCrash.txt (create one if it doesn't exist, as they are just text files).
Dave
===Windows 11 & Android 13
0 -
I'm not sure but I think the registry entry to disable logging prevents those (I got indexer error logs last night but I forgot to put the key in.
I've reformatted/rebuilt the machine (different issue: self-encrypting drives don't self-encrypt in RAID configuration) and didn't get those error logs--either the error didn't happen or I disabled logging in time.
I'll leave the crash/error logs since I can distinguish the machine by the free space reported in the log. I shouldn't expect this to be a regular occurrence. What I don't need is a log for web activity that's working properly--and constant OneDrive syncing as a result.
Logos 7 Base + Platinum Library + Now | Surface Pro 2017 | i7-7700K Desktop | i7-4800MQ Gaming Laptop | Android 7.1.2
0 -
I'm going to bump this necro thread to state that I am having the same issue in Logos 7 now in April 2019. Don't know if this is fixed in Logos 8, but Mr. West isn't the only one having issues from log files in the Documents folder.
0 -
Ryan C. Wolfe said:
I'm going to bump this necro thread to state that I am having the same issue in Logos 7 now in April 2019. Don't know if this is fixed in Logos 8, but Mr. West isn't the only one having issues from log files in the Documents folder.
“The trouble is that everyone talks about reforming others and no one thinks about reforming himself.” St. Peter of Alcántara
0
