Win32 has PIDs as usual, though they tend to be more annoying numbers, since they're really pointers into a kernel memory structure. IOW, you can use all the standard methods for dealing with this.
You can also use a Mutex kernel-object, which is the standard win32 way of dealing with it. See Win32::Mutex. This has the advantage of not creating files, and not having problems with the lockfiles of dead processes staying around. OTOH, it doesn't have the transparency that lockfiles/pidfiles do, and it's inherently nonportable.
Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).
| [reply] |
Yes, That will print the PID.
But Let me put it another way.
I am trying to put in a test in the program to stop the user from starting-up more than one instance of the program at a time. So on startup if I count more than one instance running, I can abort out. With a nice message to the user of course.
I am trying to resist the idea of pipeing out to an external program like tlist.exe or some favor of ps.exe to get the process list. | [reply] |
