Maybe I forgot to mention that this is all done through a web interface. The perl
script that is being ran is executed from a private web page. I am playing with using
"top" to gather a list of processes, but it takes it 1-2 second to get past that part
of the code. Do you know of a quicker process lister then top? All I am doing is
searching through the output from top for the program name and capture the pid# so I
can execute "kill pid#" shortly after. It works, but it just takes too long...
Bug Hunter wrote:
> Well, your button is the one that starts the script. If you have access
> to the code in the button, the button code can write the .lck file and
> then decide to spawn the perl script, or ignore the click, then the perl
> script can delete the .lck file, if the perl script is being
> run in a separate process.
>
> It sounds like to me that the perl script migh be part of the same
> script that is running due to the button click, and exiting is
> terminating both instances. In that case, simply have the second instance
> spin (it knows it is the second instance because the .lck file exists)
> until the .lck file is removed, and then exit, or do what I indicated
> above for the button code. more than one way to clean the clock.
>
> bug
