At 08:57 PM 2/28/02 +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. > >This is still somewhat less than 100% since there _could_ be an unrelated >program called mprime running, or the user might be running mprime under a >different program name. But it is sufficient to squash this particular >problem, which might be fairly common on systems where mprime is started >automatically in the system startup scripts.
It also fails (although in the other direction, starting more than one copy), if mprime has been named to something else. There are ways around that though. It could check to see if the other process has a program of the same name attached, instead of checking for mprime. _________________________________________________________________________ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
