On 02/27/2024 10:48 AM, Go Canes wrote:
I can think of 2 ways off the top of my head....
1) put the lockfile in a memory-based file system like /tmp, /run,
etc. This is probably the "correct" way.
2) compare when the system was booted against when the lock file was
created. If boot time > lock file time, lock file is stale.
Another way is to run thunderbird from a script with a name such as
tbird to avoid confusion. That script can check to see if there's a
copy of thunderbird running, and if not, delete the lock file. If there
is, of course, it just exits.