This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

ค้นหาฝ่ายสนับสนุน

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

เรียนรู้เพิ่มเติม

Lock file and version 68.8.1

  • 2 การตอบกลับ
  • 1 คนมีปัญหานี้
  • 1 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย stepbystepfarm

more options

I am thinking of moving our mail profile to a local network drive. So went to look at what locking mechanism to prevent concurrent access (I am a retired senior systems analyst). I found the parent.lock file and read about it. But is does NOT seem to be in use by 68.8.1 I can open T'Bird with the lock file present, nor does it delete it upon closing.

Has this gone away in 68.8.1 (I saw some references ti questions about the lock file specify 68.8.0 and earlier only)

If so, been replaced by a different mechanism?

I am thinking of moving our mail profile to a local network drive. So went to look at what locking mechanism to prevent concurrent access (I am a retired senior systems analyst). I found the parent.lock file and read about it. But is does NOT seem to be in use by 68.8.1 I can open T'Bird with the lock file present, nor does it delete it upon closing. Has this gone away in 68.8.1 (I saw some references ti questions about the lock file specify 68.8.0 and earlier only) If so, been replaced by a different mechanism?

การตอบกลับทั้งหมด (2)

more options

There is not locking to prevent concurrent access. Use of shared network storage is not supported, although many do use it. Most issues appear to be related to netgear NAS devices. Perhaps they are a bit more proprietary that some others.

more options

Partially answered (and the additional bit about Netgear MIGHT be relevant because I do have a Netgear router))

Was this intentional with 68.8.1? (disabling parent.lock process) It seems only partially removed as WILL create the parent.lock file when starting (if absent) just ignores checking for its presence and does not remove it on closing.

I'm afraid too much of a pro (retired now) to have it accessible from multiple machines without preventing accidental concurrent access. Will need to look at other ways around the present difficulty. Worse at the moment because of COVID resulting in frequent ZOOM etc. meetings and organizers having difficulty understanding that will be using a machine that does not have access to the email invitation.