> On 8 Feb 2019, at 23:54, John Ralls <jra...@ceridwen.us> wrote: > > > >> On Feb 8, 2019, at 2:02 PM, Michael Hendry <hendry.mich...@gmail.com> wrote: >> >> Actually, the first file was modified on 8th Feb at 00:01, followed by the >> lock file at 00:03. >> >> The MDH.gnucash.tmp-ea6yhc file isn’t a text file like the others, so I >> suspect that it’s part of the compression process that eventually results in >> a new MDH.gnucash file. >> > > That file that was touched at 00:01 is the previous session's log file as is > indicated by the timestamp in the file name.
OK, I missed that detail. It raises a question to me (probably not relevant to this problem) - why would a log file have to be modified (or just touched) at the beginning of a new session? > > Try renaming the tmp file to something ending in gz and then run gunzip on > it. Unless the gzip is borked it should turn into a text file. > After that diff it with MDH.gnucash to see what's been added or deleted. | ~/tmp/BUG @ Michaels-iMac (michaelhendry) | => gunzip temp.gz gunzip: temp.gz: unexpected end of file gunzip: temp.gz: uncompress failed Running gunzip on MDH.gnucash (appropriately renamed) expands it into an xml file, as expected. Michael _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
