Backup file lock / Quick Launch

Moz 1.6 on w98, with "Quick launch" active on w98. Backing up the "Profile Folder" over the network. Have not quite figured out the sequence "fresh boot - verse - Mozilla loaded, then closed" but the following file remains "active / locked" when Moz closed and Quick Launch is active .. Parent.Lock (root file in .slt folder). When Quick Launch is CLOSE, then the file lock is released ... but what is being added to the backup file as changed info is ".slt\prefs.bak and .slt\prefs.js ".
To make a long story short, is "parent.Lock" part of the Quick launch routine.. thus just excluding in from backup process would be the solution? Hope I have not confused you, cause I get confused just trying to explain it.
My concern, the lock is to prevent coping of .slt\prefs.bak and .slt\prefs.js because production and quick launch have different views (out of sync.)
Another solution .. is there a exe program call which closes quick launch, since the backup program can terminate running programs.

 

Dennis,
Win 98se - Moz 1.6f
As a rule I do not use QL.....

A couple of observations:
With QL enabled-Open Moz via desktop shortcut to Profile-A.
Parent.lock file created in Profile-A directory.

Close Mozilla - open Moz via QL - Whether you get the Profile Manager or not seems to be dependent on what you have selected in Profile Manager - if you have selected "Don't ask at startup" then Moz opens with the last selected profile. If you have not selected "Don't ask...." then Moz opens with "profile Manager ".



Conclusion:
"Parent.lock" file is created when there is an active profile open.

QL only loads upto the point of the "Profile Manager" What happens then is dependent of your settings in Profile manager.
edited:
Please disregard previous edit...... I am getting confused....
If Moz is closed there should be NO "parent.lock" file


As to the back up situation, it looks to me like this is a "Windows thing" - If I try and copy a directory that contains "parent.lock" file
I get a "shareing" violation from the OS....this happens whether I do a manual copy or via a batch file.....and nothing is copied...

These are just my observations, I could be, and often am, wrong.
Hope this helps a little.

regards:captjlddavis

 

Dennis,

It is safe to delete parent.lock, or if you prefer, rename the file.

parent.lock - Lock-file
Look in your profile directory for file called parent.lock, lock, or .parentlock. Delete the file. (The file is created on start-up to prevent multiple instances of Mozilla or Mozilla-based browser from accessing the same profile simultaneously. The file is destroyed on exit.)

HTH,

Ramona

 

Thanks Ramona and captjlddavis

Now that I understand the function of "parent.lock ", I've excluded it from backup process. The file carries no data (always 0 kb when active) and serves only to prevent another profile being run.
I've never liked QL, since I've seen it cause / change file data. But on the kids / wife older computer (300 Hmz / 128 MB), there is a dramatic difference in load times. Since they do no tweaking in browser files, it has never caused a problem. But QL gave me a headache for backups over the network. If there computer was on, the file was locked. Deleting or renaming has the same result, access denied. With parent.lock file excluded, backups can occur with Mozilla open, closed, or QL active. Now I can set backups on auto-schedule and capture current file(s) updates.
Thanks to you both.