At 08:57 PM 2/28/2002 +0000, Brian J. Beesley wrote: >The test could be reinforced by checking the program name associated with the >PID. If it _is_ mprime, then another copy using the same local.ini file >really _is_ running. If it _isn't_ mprime, then the PID in the local.ini file >is _wrong_ and can be ignored.
mprime should only raise this error if the pid in the local.ini file and the current pid are both running mprime (actually comparing the inode values). If there are any Linux experts that can tell me where this test is going wrong, I'd appreciate any insights. This is the first reported failure in 2 years. _________________________________________________________________________ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
