Re: Log File behaviour
On Thu, Jun 15, 2000 at 07:41:29PM -0500, Richard Wackerbarth wrote: On Thu, 15 Jun 2000, Dave Peticolas wrote: Now, those .xac files - are they the previous data file, or are they written in parallel with the main file? (Or copied after the main file is written?) They are written immediately after the main file is written. So, if I have (only) a main file and start to edit it, are you saying that at the end, I have two copies of the modified file and NO copies of the original? Furthermore, while the main file is being written, there is no valid copy of the data? Surely at least the backup files should be written _before_ the main file is modified. You would still have the backup file that was created *last time*. --Dylan Thurston [EMAIL PROTECTED] -- Gnucash Developer's List To unsubscribe send empty email to: [EMAIL PROTECTED] -- Gnucash Developer's List To unsubscribe send empty email to: [EMAIL PROTECTED]
Re: Log File behaviour
On Sun, 18 Jun 2000, Hendrik Boom wrote: On Thu, Jun 15, 2000 at 07:41:29PM -0500, Richard Wackerbarth wrote: On Thu, 15 Jun 2000, Dave Peticolas wrote: Now, those .xac files - are they the previous data file, or are they written in parallel with the main file? (Or copied after the main file is written?) They are written immediately after the main file is written. So, if I have (only) a main file and start to edit it, are you saying that at the end, I have two copies of the modified file and NO copies of the original? Furthermore, while the main file is being written, there is no valid copy of the data? Surely at least the backup files should be written _before_ the main file is modified. You would still have the backup file that was created *last time*. Only if you KNOW to save it. From the user's perspective "rm XX.*" is certainly the intutive thing to do. Since the program reads all the data into memory and doesn't write it until you ask, mos users would expect the original input file to be preserved since that is the way most programs do it. -- Gnucash Developer's List To unsubscribe send empty email to: [EMAIL PROTECTED]
Re: Log File behaviour
On Thu, Jun 15, 2000 at 07:41:29PM -0500, Richard Wackerbarth wrote: On Thu, 15 Jun 2000, Dave Peticolas wrote: Now, those .xac files - are they the previous data file, or are they written in parallel with the main file? (Or copied after the main file is written?) They are written immediately after the main file is written. So, if I have (only) a main file and start to edit it, are you saying that at the end, I have two copies of the modified file and NO copies of the original? Furthermore, while the main file is being written, there is no valid copy of the data? Surely at least the backup files should be written _before_ the main file is modified. --Dylan Thurston [EMAIL PROTECTED] -- Gnucash Developer's List To unsubscribe send empty email to: [EMAIL PROTECTED]
Re: Log File behaviour
Richard Wackerbarth writes: On Thu, 15 Jun 2000, Dave Peticolas wrote: Now, those .xac files - are they the previous data file, or are they written in parallel with the main file? (Or copied after the main file is written?) They are written immediately after the main file is written. So, if I have (only) a main file and start to edit it, are you saying that at the end, I have two copies of the modified file and NO copies of the original Yes, that's right. dave -- Gnucash Developer's List To unsubscribe send empty email to: [EMAIL PROTECTED]
Re: Log File behaviour
On Fri, 16 Jun 2000, Dave Peticolas wrote: Richard Wackerbarth writes: On Thu, 15 Jun 2000, Dave Peticolas wrote: Now, those .xac files - are they the previous data file, or are they written in parallel with the main file? (Or copied after the main file is written?) They are written immediately after the main file is written. So, if I have (only) a main file and start to edit it, are you saying that at the end, I have two copies of the modified file and NO copies of the original Yes, that's right. I could recommend another strategy :-) -- Gnucash Developer's List To unsubscribe send empty email to: [EMAIL PROTECTED]
Re: Log File behaviour
Richard Wackerbarth writes: On Fri, 16 Jun 2000, Dave Peticolas wrote: Richard Wackerbarth writes: On Thu, 15 Jun 2000, Dave Peticolas wrote: Now, those .xac files - are they the previous data file, or are they written in parallel with the main file? (Or copied after the main file is written?) They are written immediately after the main file is written. So, if I have (only) a main file and start to edit it, are you saying that at the end, I have two copies of the modified file and NO copies of the original Yes, that's right. I could recommend another strategy :-) Yes, we might want to think about just copying the original to the backup file, rather than making a trail of 'save histories'. OTOH, when we move to using sleepycat db, as it seems we probably will, there may be an even better solution using that tool. dave -- Gnucash Developer's List To unsubscribe send empty email to: [EMAIL PROTECTED]
Re: Log File behaviour
On Fri, 16 Jun 2000, Dave Peticolas wrote: Richard Wackerbarth writes: I could recommend another strategy :-) Yes, we might want to think about just copying the original to the backup file, rather than making a trail of 'save histories'. You can have both by having a trail of backups. OTOH, when we move to using sleepycat db, as it seems we probably will, there may be an even better solution using that tool. I don't think that gnucash should dictate a single strategy. The strategy is a function of the storage mechanism and we should remain neutral. -- Gnucash Developer's List To unsubscribe send empty email to: [EMAIL PROTECTED]
Log File behaviour
Hi, I'm looking to replicate my stability problems in 1.3.99, so I'm looking over my log files to try to come up with a duplicate account set. I've got the following files: MyMoney.gnucash.2609091831.xac MyMoney.gnucash.2611151831.log - Opened up for a peek - no changes MyMoney.gnucash.2611165154.log - Crash occurred at the end of this file MyMoney.gnucash.2611220759.log - Here I re-entered the data MyMoney.gnucash.2611221115.xac - Paranoid saving from here MyMoney.gnucash.2611221355.xac MyMoney.gnucash.2611221600.xac MyMoney.gnucash.2611222123.xac MyMoney.gnucash.2611222504.xac MyMoney.gnucash.2611223124.xac MyMoney.gnucash.2611223356.xac MyMoney.gnucash.2611223828.xac MyMoney.gnucash.2611224103.xac MyMoney.gnucash.2611230056.xac MyMoney.gnucash.2611230133.log MyMoney.gnucash.2611230206.xac MyMoney.gnucash.2611230255.xac MyMoney.gnucash.2611231002.xac MyMoney.gnucash.2611231315.log MyMoney.gnucash.2611231932.xac MyMoney.gnucash.2611232314.xac MyMoney.gnucash.2613072433.log I'm assuming that a log file is created every time I start GNUcash, and that things are written to it as I use it. Now, those .xac files - are they the previous data file, or are they written in parallel with the main file? (Or copied after the main file is written?) While I think of it, I've managed to corrupt a main file once. I recovered simply by copying over the most recent .xac backup file. However, we should put into place a mechanism for avoiding this. The usual practice in Mac programming is to: 1. Create a temporary in the same directory as you wish to write to 2. Write to this file 3. When it completes sucessfully, swap the temporary file and the original file 4. If not successful, warn user. 5. Delete temporary file. This is made easy on the mac with a system call for swapping over two files - I presume that it just swaps the pointers from the directory entries. This would also detect running out of disk space. At least the user would find out before losing their original file. Ben. -- Ben Stanley |barf [ba:rf] 2. "He suggested using FORTRAN, PhD Student | and everybody barfed." - From the Shogakukan SITACS| DICTIONARY OF NEW ENGLISH (Second Edition) University of Wollongong | Australia |http://www.uow.edu.au/~bds02 -- Gnucash Developer's List To unsubscribe send empty email to: [EMAIL PROTECTED]
Re: Log File behaviour
Ben Stanley writes: Hi, I'm looking to replicate my stability problems in 1.3.99, so I'm looking over my log files to try to come up with a duplicate account set. I've got the following files: MyMoney.gnucash.2609091831.xac MyMoney.gnucash.2611151831.log - Opened up for a peek - no changes MyMoney.gnucash.2611165154.log - Crash occurred at the end of this file MyMoney.gnucash.2611220759.log - Here I re-entered the data MyMoney.gnucash.2611221115.xac - Paranoid saving from here MyMoney.gnucash.2611221355.xac MyMoney.gnucash.2611221600.xac MyMoney.gnucash.2611222123.xac MyMoney.gnucash.2611222504.xac MyMoney.gnucash.2611223124.xac MyMoney.gnucash.2611223356.xac MyMoney.gnucash.2611223828.xac MyMoney.gnucash.2611224103.xac MyMoney.gnucash.2611230056.xac MyMoney.gnucash.2611230133.log MyMoney.gnucash.2611230206.xac MyMoney.gnucash.2611230255.xac MyMoney.gnucash.2611231002.xac MyMoney.gnucash.2611231315.log MyMoney.gnucash.2611231932.xac MyMoney.gnucash.2611232314.xac MyMoney.gnucash.2613072433.log I'm assuming that a log file is created every time I start GNUcash, and that things are written to it as I use it. Now, those .xac files - are they the previous data file, or are they written in parallel with the main file? (Or copied after the main file is written?) They are written immediately after the main file is written. dave -- Gnucash Developer's List To unsubscribe send empty email to: [EMAIL PROTECTED]
Re: Log File behaviour
On Thu, 15 Jun 2000, Dave Peticolas wrote: Now, those .xac files - are they the previous data file, or are they written in parallel with the main file? (Or copied after the main file is written?) They are written immediately after the main file is written. So, if I have (only) a main file and start to edit it, are you saying that at the end, I have two copies of the modified file and NO copies of the original? -- Gnucash Developer's List To unsubscribe send empty email to: [EMAIL PROTECTED]
