When does GnuCash create .log files?

[David Carlson]

I have experimented further after reading your post DaveC49.

In my case, I am keeping the data file on a remote server and I see that
the .log file grows as I edit my data, but the modified time stays at the
time created for some reason.  I also set GnuCash to ask me before doing an
auto-save and that seems to have stopped the surprise auto-saves.  I had
set the interval to 30 minutes because it takes forever to do a full save
to the remote server and that had been interrupting me when I was doing a
lengthy OFX import or a reconcile.  I think that your .LNK file is
something that Linux does in the background sometimes, as it is essentially
a copy of a file in a different location.

Now that I understand it better, I think that I can live with the auto-save
if I turn the warning back on.  I do wish that the documentation was more
technically accurate, especially for users that keep their data somewhere
other than their user space on their 'C' drive.

David C

On Tue, May 16, 2017 at 7:09 PM, DaveC49 <davidcousens at bigpond.com> wrote:

> To be useful the logfiles should be being written as each transaction is
> recorded rather than only at the end of a session. In the latter case if a
> crash/programming fault causes Gnucash to exit abnormally the log file
> would
> contain no useful information. Autosave should only be working on the main
> data file and not the logfiles.
>
> I have just closed down gnucash at 09:39:54 local time.
> date Modified
> The logfile is named:        TestBooksBudget.gnucash.20170517093954.log
> Tue 16th May 2017 18:49:11 AEST
> The last backup is named:TestBooksBudget.gnucash.20170517093954.gnucash
> Wed 17th May 201709:39:54 AEST
> The current file is :          TestBooksBudget.gnucash
> Wed 17th may 2017 09:39:54 AEST
>
> The previous logfile:        TestBooksBudget.gnucash.20170516184911.log
> Wed 17th May  2017 09:39:39 AEST
> The previous backup:     TestBooksBudget.gnucash.20170516184911.gnucash
> Tue 16th May 2017 18:44:10 AEST.
>
> If I now open Gnucash the backup file remains the same as the above at this
> point.
> A new log file is opened  TestBooksBudget.gnucash.20170517095417.log
> Wed 17th May 2017 09:54:17 AEST
> The previous data file is renamed:
>
> TestBooksBudget.gnucash.20170517095918.gnucash    Wed 17th May 2017
> 09:59:18
> AEST. ( the time difference is most likely that required to open and read
> the previous data file.
>
> A file TestBooksBudget.gnucash.ffffffffa8c00400.13920.LNK Wed 17th May
> 2017
> 09:54:17 AEST is also created when the file is reopened along with the lock
> file,  TestBooksBudget.gnucash.LCK Wed 17th May 2017 09:54:17 AEST. Have no
> idea yet what the first file does?
>
> This tends to support the view that the logfile is opened at the start of a
> new gnucash session and then transactions are written to it as they occur.
>
> I have an autosave interval of 5 mins.
>
> A new back up file TestBooksBudget.gnucash.20170517095918.gnucash Wed 17th
> May 2017 09:39:54 AEST and a new log file
> TestBooksBudget.gnucash.20170517095918.log Wed 17th May 2017 09:59:18 are
> created at the end of the autosave interval.
>
> (Gnucash 2.6.16  on Linux Mint 18.1)
>
> David Cousens
>
>
>
> --
> View this message in context: http://gnucash.1415818.n4.
> nabble.com/When-does-GnuCash-create-log-files-tp4691667p4691675.html
> Sent from the GnuCash - User mailing list archive at Nabble.com.
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>