On 12/6/24 7:14 PM, Stephen Morris wrote:
On 7/12/24 13:28, Samuel Sieb wrote:
There's nothing accumulating here. The lock file is checked at
application startup. If it's still valid, then the new process will
not start, probably passing information to the existing process. If
it's not valid, then the old lock is deleted and a new one created.
Standard practice, just using a symlink instead of a file.
What determines that the lock file is valid? In the case of Thunderbird
where it creates a lock file in folder for my profile and the folder
where Thunderbird is installed to, the symlinks are dangling while
Thunderbird is running, if firefox is the same while firefox is running
the lock symlink is dangling and after firefox shuts down it is left
there dangling, hence what determines whether or not it is valid?
It's not actually a link, so it's not "dangling". It's just
information. The information is an IP address and a process id. I'm
not sure how the IP address is used, but the process id is how it knows
if it's valid. If the process exists, it's valid.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
