SyMenu Forum

SyMenu

 

HomeGeneral discussion & questions

Talk about SyMenu or post suggestions, requests, or how-to questions

SQLite log file - LogActivities.sqlite3 Messages in this topic - RSS

JM
JM
Posts: 3


29 days ago
JM
JM
Posts: 3
With both log options unchecked in the advanced options, still get a LogActivities.sqlite3 file created and held open. This causes me grief as I have my Symenu located on MS OneDrive and it complains about LogActivities.sqlite3 being held open. I've been unsuccessful at getting OneDrive to ignore (not Symenu's challenge). Question: is there a configuration option to disable SQLlite use if you'r enot logging? Short of that, is there a way to direct the log files to a different directory?
Thank you
+1 link
Gianluca
Gianluca
Administrator
Posts: 956


29 days ago
Gianluca
Gianluca
Administrator
Posts: 956
You are right... the expected behavior is to log nothing if you uncheck the two log options.

I need to investigate the code because it's probably a little bug.
If I find it, you'll get a fix directly on the next version.
Thank you for reporting it.
link
Gianluca
Gianluca
Administrator
Posts: 956


29 days ago
Gianluca
Gianluca
Administrator
Posts: 956
OK I've just checked the code.

Even if you disable the two options I need to know several things:
1) the folder existence. If it doesn't exist it'll be created;
2) the tables existence;
3) the write permission on folder and db file.


I can't avoid these checks because you are allowed to change the log options during the program execution and I need to be ready for this on the fly change.
Anyway your workaround is not to wait for my modify, that I probably won't do, but to put the log folder in read-only state.

If it works, please report that here.
link
JM
JM
Posts: 3


25 days ago
JM
JM
Posts: 3
Gianluca wrote:
OK I've just checked the code.

Even if you disable the two options I need to know several things:
1) the folder existence. If it doesn't exist it'll be created;
2) the tables existence;
3) the write permission on folder and db file.


I can't avoid these checks because you are allowed to change the log options during the program execution and I need to be ready for this on the fly change.
Anyway your workaround is not to wait for my modify, that I probably won't do, but to put the log folder in read-only state.

If it works, please report that here.


Gianluca - Thank you for reviewing the code and suggesting a work around. I can report that the work around is effective.
I started Symenu and let it create Log and Log/LogActivities.sqlite3
I exited Symenu
Waited for OneDrive to complete sync
Set Read Only on Log and Log/LogActivities.sqlite3
Waited for OneDrive to complete sync
Started Symenu - no errors or other msgs

I'll report back if there are ramifications during other activities.

As a permanent fix to this (I assume other sync technologies would have similar challenges), could you add the ability to set the log path as a configuration option? My strategy in using Symenu is to make apps portable across Windows instances and minimize my rebuild time when I have to swap out my device. So putting Symenu on my OneDrive was a significant part of that strategy.

Thank you
Jon
link
Gianluca
Gianluca
Administrator
Posts: 956


25 days ago
Gianluca
Gianluca
Administrator
Posts: 956
As you can see here https://www.ugmfree.it/SyMenuManual.aspx#CommandLine SyMenu already grants a lot of path customizations.

It's not a problem to add the path for the log this way, but you should use a customized shortcut with a new command line parameter to execute SyMenu. I don't know if you'd be willing to do that.

Anyway, I'm a power user of Dropbox and I have a similar problem with several folders (not a SyMenu thing anyway).
The solution in Dropbox and in any other synchronization tool is to use the selective sync.
Here's the OneDrive solution for this: https://support.office.com/en-us/article/choose-which-onedrive-folders-to-sync-to-your-computer-98b8b011-8b94-419b-aa95-a14ff2415e85
link
cogmios
cogmios
Posts: 3


3 days ago
cogmios
cogmios
Posts: 3
I came here for this issue and found this thread smile
In my case: the onedrive location where the symenu resides is a shareable location "drive" that all laptops share of multiple persons.

I noticed that the onedrive sync tool indeed reported this on all machines.
I notice in this folder both logactivities and logactivities followed by the specific name of them machine, assuming these are onedrive remnants or maybe it creates them a new for each user?

So if I understand correctly the log sql file will need be put read-only on every machine where it is installed?

edited by cogmios on 19/01/2020
link
Gianluca
Gianluca
Administrator
Posts: 956


1 days ago
Gianluca
Gianluca
Administrator
Posts: 956
cogmios wrote:
So if I understand correctly the log sql file will need be put read-only on every machine where it is installed?

It's one solution but you have others.

For example you can set the entire Log folder to read only. This way you prevent a future creation of other files (unplanned).

You can tell OneDrive not to sync the Log folder.

Plus with the next version, that is just a few days away, you'll have a new command line parameter to redirect the Log folder in another location of your choice.

Anyway I think the most correct way to operate is removing the Log folder from sync.
link
JM
JM
Posts: 3


1 days ago
JM
JM
Posts: 3
Gianluca wrote:
As you can see here https://www.ugmfree.it/SyMenuManual.aspx#CommandLine SyMenu already grants a lot of path customizations.

It's not a problem to add the path for the log this way, but you should use a customized shortcut with a new command line parameter to execute SyMenu. I don't know if you'd be willing to do that.

Anyway, I'm a power user of Dropbox and I have a similar problem with several folders (not a SyMenu thing anyway).
The solution in Dropbox and in any other synchronization tool is to use the selective sync.
Here's the OneDrive solution for this: https://support.office.com/en-us/article/choose-which-onedrive-folders-to-sync-to-your-computer-98b8b011-8b94-419b-aa95-a14ff2415e85



For whatever reason, I don't seem to get notifications when you reply, so this is way late.
My experience with OneDrive selective sync has not been fruitful - if you uncheck the dir (supposedly won't sync dir and files contained) you end up in an endless loop whereby you have to remove the dir/files from onedrive, but when you do that you can't deselect for sync. Symenu then creates the dir and file on next use and onedrive then syncs...on and on and on...I see from the next message that you plan to release with the config option to direct - this is good news! Thank you.
I am not experiencing any negative affects from the workaround with readonly.
thank you
link
Gianluca
Gianluca
Administrator
Posts: 956


1 days ago
Gianluca
Gianluca
Administrator
Posts: 956
JM wrote:
I see from the next message that you plan to release with the config option to direct - this is good news! Thank you.

Indeed it'll be a command line parameter solution not a config one. But it'll solve the Log path customization issue the same.

It's incredible that OneDrive is not able to manage a simple sync exception.


When you unsync a folder, Dropbox too removes it, but if you create the folder again, DB understands that you want to have it and leaves it on your FS without synchronizing it.
IMHO it's not perfect (why the hell it needs to remove it locally when you unsync it???) but if you follow its rules, it works.
link



UGMFree.NET ©2002-2020
By Gianluca Negrelli - Contact me