Welcome Guest.   Make a donation to an author on the site April 23, 2014, 02:54:51 PM  *

Please login or register.
Or did you miss your validation email?


Login with username and password (forgot your password?)
Why not become a lifetime supporting member of the site with a one-time donation of any amount? Your donation entitles you to a ton of additional benefits, including access to exclusive discounts and downloads, the ability to enter monthly free software drawings, and a single non-expiring license key for all of our programs.


You must sign up here before you can post and access some areas of the site. Registration is totally free and confidential.
 
Read the Practical Guide to DonationCoder.com Forum Search Features
   
   Forum Home   Thread Marks Chat! Downloads Search Login Register  
Pages: [1]   Go Down
  Reply  |  New Topic  |  Print  
Author Topic: Linkman save methodology  (Read 1060 times)
Steven Avery
Supporting Member
**
Posts: 657

View Profile Give some DonationCredits to this forum member
« on: July 24, 2012, 06:41:01 AM »

Hi,

Many of you, like me, probably use Linkman as an all-purpose PIM and information repository, as well as bookmarks.  There is one behaviour I noticed that I want to discuss with the Donationcoder experts.

Linkman has a method of saving to backup files with extensions like .ba0, .ba1, etc.  And this is very helpful for giving you access to a recent copy in case of things like a crash.  You have flexibility as to the frequency of the saves, I choose about 10 minutes, not after every add.

What I find perplexing is that the main file .lmd often is behind the .ba_ files when you reopen Linkman after crashes (this can be a Windows forced reboot, or an occasional Linkman lockup) ... and maybe, at times,  even after exiting the program normally.

What I do in that case, if I remember the problem, is go to the backup files in Total Commander, see which is the biggest ( ba0 ) and then rename the .lmd file to .aaa (or anything) and rename the .ba0 file to .lmd .  Thus I have data that is up-to-date.

However, this seems strange to me, that the .lmd file gets so far behind. That it is not updated at the time of the saves. I've discussed this a bit with Thomas from Linkman, without succeeding in getting him to agree that this is unusual.  Now there may be a problem updating the .lmd file which is in memory, that is a techie question. However, do a test, sometimes I think the problem even exists on normal "exits" (at least it has seemed that way to me), where there is not a memory issue.

So your experiences and perspective is welcome. 
Am I missing something ? Is there something that should be improved ?

Thanks.

Shalom,
Steven Avery
Logged
Outertech Support
Member
**
Posts: 168


View Profile Give some DonationCredits to this forum member
« Reply #1 on: March 15, 2013, 12:50:16 AM »

Steven, as discussed in the email, save works like this:

database.ba1 is renamed to database .ba2
database.ba0 is renamed to database .ba1
database.lmd is renamed to database .ba0

this happens before writing anything.

then the new database.lmd is written.

In case of a system crash/file system error, the .lmd file could be smaller than .ba0 file if the .lmd file was not written correctly/to the end.

Logged
Steven Avery
Supporting Member
**
Posts: 657

View Profile Give some DonationCredits to this forum member
« Reply #2 on: March 21, 2013, 02:47:16 PM »

Hi,

I really have not had the problem mentioned above for a few months.
Why I had it before is a puzzle, but one that for now can sit in the dustbin of history.  

Steven
Logged
Pages: [1]   Go Up
  Reply  |  New Topic  |  Print  
 
Jump to:  
   Forum Home   Thread Marks Chat! Downloads Search Login Register  

DonationCoder.com | About Us
DonationCoder.com Forum | Powered by SMF
[ Page time: 0.023s | Server load: 0.08 ]