Rob,
I think you're right. I think the idea would be to have the server name
next-to-be-processed append to the file, then the next step call a single
separate script (start it if not already running, otherwise simpley "wait")
that would lock the "control file", and this script would be the singl
Jeff Westman wrote:
> I'm posed with a problem, looking for suggestions for possible resolution. I
> have a script that has many steps in it, including telnet & ftp sessions,
> database unloads, and other routines. This script will run on a server,
> accessing a remote server. This works fine.
Jeff Westman wrote:
I'm posed with a problem, looking for suggestions for possible resolution. I
have a script that has many steps in it, including telnet & ftp sessions,
database unloads, and other routines. This script will run on a server,
accessing a remote server. This works fine. I will l
Hello,
maybe you can use flock
perldoc -f flock
I have never used this and dont know if it works in your case.
/Stefan
> I'm posed with a problem, looking for suggestions for possible resolution. I
> have a script that has many steps in it, including telnet & ftp sessions,
> database unloads,
I'm posed with a problem, looking for suggestions for possible resolution. I
have a script that has many steps in it, including telnet & ftp sessions,
database unloads, and other routines. This script will run on a server,
accessing a remote server. This works fine. I will likely have several
d
