On Tue, 28 Mar 2000, you wrote:
> How about the plain old lock-file trick? First thing the script does is check if
> a file called 'lock' or something, exists. If not, it creates an empty file
> called 'lock', and continues. When it's finished, it deletes the file. All you
> have to do is make sure that you check for the files existance in the beginning
> of the script, and use a simple 'if' to determine if it will continue, or die
> right there and then.
>
How about a shell script to call the perl script? Use the
shell script to create the lock file and then call the perl
script as well as delete the lock file AFTER the perl
script exits, or have the perl script delete the lock file
as the last thing it does???
John
- Re: [expert] Multiple Processes Michael D. Kirkpatrick
- Re: [expert] Multiple Processes Bug Hunter
- Re: [expert] Multiple Processes Michael D. Kirkpatrick
- Re: [expert] Multiple Proces... Bug Hunter
- Re: [expert] Multiple Proces... Rial Juan
- [expert] Wrong options used ... jwang
- Re: [expert] Multiple Proces... Charles Curley
- Re: [expert] Multiple Processes Rial Juan
- RE: [expert] Multiple Processes Ken Wilson
- Re: [expert] Multiple Processes Rial Juan
- Re: [expert] XFree86 version 4 and the SI... John Aldrich
- Re: [expert] XFree86 version 4 and the SIS 6326 ch... Trevor Farrell
- Re: [expert] XFree86 version 4 and the SIS 63... Leonardo T. de Carvalho
- Re: [expert] XFree86 version 4 and the SI... Dennis Robertson
- Re: [expert] XFree86 version 4 and the SIS 63... Dennis Robertson
- Re: [expert] XFree86 version 4 and the SI... Trevor Farrell
- [expert] XFree86 version 4 and the SIS 6326 chip Dennis Robertson
