Why the change in logs folder settings with 10.3?

Discuss new features and functions
User avatar
Plerry
Posts: 659
Joined: 22 Aug 2012

Post by Plerry • 28 Aug 2018, 14:43

@GordonFFS:
There was no need to copy/paste your earlier message.
I pointed you here because, as you could have read above, the issue will be resolved in V10.4, which you can verify with a Beta release of V10.4.
For your problem: simply keep using V10.2 until V10.4 is released.

josvliet
Posts: 1
Joined: 28 Aug 2018

Post by josvliet • 28 Aug 2018, 14:52

Please, please, undo the log file restrictions as introduced in version 10.3 and set everything (according to log files) back as it was in version 10.2.

cybermcm
Posts: 3
Joined: 9 Aug 2018

Post by cybermcm • 10 Sep 2018, 06:11

Thank you for changing the log file options in 10.4! Really appreciated!

randomofamber
Posts: 2
Joined: 9 Aug 2018

Post by randomofamber • 11 Sep 2018, 08:33

Thank you for possibility override default log path in version 10.4 .

rh1
Posts: 3
Joined: 13 Feb 2018

Post by rh1 • 11 Sep 2018, 12:40

Hi,
I experienced the problem (for me) with the changed logfile directory. In my home environment I ask my family members to check the logfile for the daily batch jobs, which were configured to be found in the users home directory.

Now I'm trying the 10.4 where this should be fixed but I cannot find a place, where and how I can change the logpath.
In earlier versions there was a possibility when I used the "save as batch" dialog. There is no now.
The default path in the options menu cannot be changed. "Overriding" mentioned in the previous post by typing something in does not work and the icon in front of the path field has no function.

It would be great, if one can point me to the location where and how I can change the logfile path for specific batch jobs.

cybermcm
Posts: 3
Joined: 9 Aug 2018

Post by cybermcm • 11 Sep 2018, 14:22

The option can be found in the "Synchronization" settings of the batch job
Image

rh1
Posts: 3
Joined: 13 Feb 2018

Post by rh1 • 11 Sep 2018, 15:07

Thanks!!! Very helpful for blind people instaed of many words :-)

I didn't find/recognize this as I did not change the jobs I'm using and for testing I did not check all menus.

GordonFFS
Posts: 6
Joined: 14 Dec 2016

Post by GordonFFS • 11 Sep 2018, 16:02

Just tried v10.4 and once-again I've returned to v10.2.
It's nice to be able to change the logfile path (allthough I don't need it).
But the logfiles still have generated names (the name of the ffs-command-file followed by a timestamp).
In my scripts I just simply read the fixed-name "LastSyncs.log".

May I suggest a changable logfilename. Many programs use so-called 'placeholders'. Something like "LastSyncs %FN %TS.log" (%FN will be substituted with the name of the the ffs-command-file and %TS would be substituted by a TimeStamp). I my case I would remove the placeholders and end up with the old-fixed-filename "LastSyncs.log".

timgeorgeprice
Posts: 1
Joined: 14 Sep 2018

Post by timgeorgeprice • 14 Sep 2018, 03:10

My situation the same as GordonFFS, so seconding that request, and much appreciated if you can do it for us please. Either way, thank you Zenju for all your work - FreeFileSync is simply fantastic software!

fefisy
Posts: 6
Joined: 13 Oct 2018

Post by fefisy • 14 Oct 2018, 05:14

Zenju wrote:
11 Aug 2018, 09:00
What about the deprecation and removal of "%AppData%\FreeFileSync\LastSyncs.log"? No complaints, anyone?
I don't know if this question was answered. As of v. 10.5, the fixed "default log path" does not work well. I've described the issue here with screenshots of the errors. The following is from that thread:
I realize that having the logs written to the installation directory makes sense for portable installations, but I don't see a way to alter the default log path for a desktop installation. /opt is not normally writable by users, nor should it be. Writing logs in a single, global location also does not work well if I need to use FFS as multiple users -- in my case, for instance, I have created two users for myself, one for personal use and the other for professional, and I need to keep the logs for these separate.
I'm OK with the removal of LastSyncs.log. That is separate from the issue with the current default log path. I see that it can be overridden in batch configurations but the default should not be in the installation directory (except perhaps for portable installations) -- and ideally the user should be able change this default value as well as override it in a batch configuration. In Linux an appropriate default location would be ~/.FreeFileSync; other operating systems have similar conventions for user-specific application files.

GordonFFS
Posts: 6
Joined: 14 Dec 2016

Post by GordonFFS • 05 May 2019, 08:24

I'm still at v10.2 (after trying v10.11) because of the newly generated timestamped log filename (in stead of the needed fixed name LastSyncs.log).

Anybody an idea on how to persuade the author to combine best of both worlds?

I've tried this - in the Override default log path - hoping to trick FSS:
C:\Users\Gordon\AppData\Roaming\FreeFileSync\Logs\%date%\LastSyncs.log
No succes because I ended up with this file:
"C:\Users\Gordon\AppData\Roaming\FreeFileSync\Logs\2019-05-05\LastSyncs.log\2019-05-05 095612.754.log"

Why hold on to a generated log filename? FFS support Macros! So in stead off a Override default log path, why not a (non-checkboxed) field: Default log filename. Which - by default - looks like this: %AppData%\FreeFileSync\Logs\%timestamp%.log and can be changed (by users like me) to %AppData%\FreeFileSync\Logs\LastSyncs.log

Just my 50 cents on how to keep everybody happy with a flexible solution.

Have a nice day.

User avatar
Zenju
Site Admin
Posts: 4955
Joined: 9 Dec 2007

Post by Zenju • 12 May 2019, 09:25

GordonFFS wrote:
05 May 2019, 08:24
needed fixed name LastSyncs.log
The current behavior can certainly be improved, but for the record: Placing the following in the "Run a command" field in sync settings will do:

Code: Select all

cmd.exe /c copy "%logfile_path%" "%AppData%\FreeFileSync\LastSyncs.log"