Firefox profile stored on NAS - parent.lock problem
Hello, in our house we have 3 personal computers and there are 6 users. I have moved all user profiles to NAS. It includes Desktop, My documents, Firefox and Thunderbird profiles, etc. File "profiles" stored in C:\Users\...\AppData\Roaming\Mozilla\Firefox is same for every user: [Install308046B0AF4A39CB] Default=\\xxx.xxx.xxx.xxx\Home\Firefox Locked=0
[Profile0] Name=default IsRelative=0 Path=\\xxx.xxx.xxx.xxx\Home\Firefox Default=1
[General] StartWithLastProfile=1 Version=2
Sometimes, when user starts computer, then Firefox error message appears: "Firefox is already running..." I am sure user is not running Firefox on two computers at the same time.
In my opinion, it is problem of improper closing of Firefox, even sequence "Close Firefox, when it is closed shutdown Windows" is followed. So far I solved it by deleting parental.lock file, but it is not easy job for every user. Could you tell me what I made wrong or maybe it is something beyond me?
Thank you in advance for support.
Όλες οι απαντήσεις (2)
Does this only happen if a different user start Firefox?
Could be a problem with toolkit.startup.last_success as stored in prefs.js that doesn't match the timestamp of parent.lock See kPrefLastSuccess:
See also:
Note that the parent.lock (Windows) or .parentlock (Linux, Mac) file is no longer removed in order to detect startup failures (crashes) and offer to start in Safe mode.
Thank you for answer, however I am not sure, I understand your question properly. Let me present following scenarios: 1. Firefox launched by User 1 on PC 1, while Firefox was launched by User 2 on PC 2. Everything is OK. 2. Firefox launched by User 1 on PC 1. Firefox closed.. User 1 logged off. Firefox launched by User 2 on PC 1. Everything is OK. 3. Firefox launched by User 1 on PC 1. Firefox closed. System closed on PC 1. System started on PC 1. Firefox launched by User 1 on PC 1. Error " Firefox is already running..." I have tested logging on two PC at the same time. Firefox launched on PC 2 while alteady running on PC 1. Erorr appearance on second PC is fully understandable and acceptable.