Another mprime is already running

tshinozk · 2013-12-10, 14:37

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.

pinhodecarlos · 2013-12-10, 15:38

Offtopic. Are you the Seventeen or Bust top Producer?

Prime95 · 2013-12-10, 16:07

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

Prime95 · 2013-12-10, 16:26

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?

2013-12-10, 14:37	#1
tshinozk Nov 2012 Japan 5·7 Posts	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.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
GUI for Mprime/running Prime95 under WINE?	ixfd64	Software	5	2011-02-16 15:21
Running mprime on fedora	jimmychauck	Information & Answers	1	2010-06-16 04:42
adding a computer running mprime	Unregistered	Information & Answers	14	2009-02-16 14:01
mprime is running but i dont see that	mhnaras	Linux	2	2007-10-21 15:58
running mprime on a computer I do not own	happyraul	Software	4	2004-05-06 15:54

2013-12-10, 15:38	#2
pinhodecarlos "Carlos Pinho" Oct 2011 Milton Keynes, UK 12012₈ Posts	Offtopic. Are you the Seventeen or Bust top Producer?

2013-12-10, 16:07	#3
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 2²·13·157 Posts	In the next release I'll check that filedata.st_dev also matches.

2013-12-10, 16:26	#4
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 2²×13×157 Posts	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?