Another mprime is already running
 

I have several machines where mprimes are running.
Each mprime started automatically from a start-up script in the boot sequence.

I found that the mprime shows very occasionally "Another mprime is already running!" and the mprime do not run.
I checked if duplicate processes of the mprime are running, but I did not find another process of mprime.
After it happens, I run the mprime again manually, the mprime is successfully running.
I find that it happens after accidently reboot of the system.
I see a process ID entry in local.txt. The entry has the old process ID, but it may be no problem.

I see the source code.
mprime compares i-nodes of the processes of the old PID and the running PID.
It does work well in simple systems.
My machines have multiple HDDs and multiple partitions.
The value of i-node is unique in a single file system.
Maybe, the i-node of mprime in my secondary disk conflicts to an i-node of a program in root partition.

Thanks.

Offtopic. Are you the Seventeen or Bust top Producer?

In the next release I'll check that filedata.st_dev also matches.

The problem may be due to inode being defined as 32-bits (at compile time) where your filesystem is 64-bits.

Can a Linux expert look at the code and recommend the most portable way to use fstat -- keeping in mind that the source code is used to build both 32-bit and 64-bit executables?