Script creating best practices question?
Hello everyone,
I was in the process of creating a simple script to follow up with a file sync. So I fire off the file sync to distribute a document to a specific label. Then I wanted to have my script verify that the document had found it's destination. If the verification had succeeded then I wanted to copy and move some other files then finally delete the old directories. If it had failed then it was to initiate the file sync and get the document. My first question is would it be best just to right a batch file to handle the file moves and directory deletions, or would it be best to use the built in task functions to fire up the command line and do it that way? I had tried to use the built in task functions and went to test my scripts, and I thought it would be best to test the verification process first on two test machines before proceeding. The first run of the script came back fine saying that it had found the file on the one and the other one it initiated the sync then found the file. I added in more functionality to the script and fired that one off. In the logs I could see that the updated script had failed due to some fat fingering on my part with the directory locations. After fixing the directory locations I fired the script again just to have it hang out in limbo. The logs say that the script has pushed and it is waiting on either a success of a fail, but I checked the local directory for the script on the test machine just to see an empty folder. Does anyone know how to cancel the attempts that are not doing anything?
I was in the process of creating a simple script to follow up with a file sync. So I fire off the file sync to distribute a document to a specific label. Then I wanted to have my script verify that the document had found it's destination. If the verification had succeeded then I wanted to copy and move some other files then finally delete the old directories. If it had failed then it was to initiate the file sync and get the document. My first question is would it be best just to right a batch file to handle the file moves and directory deletions, or would it be best to use the built in task functions to fire up the command line and do it that way? I had tried to use the built in task functions and went to test my scripts, and I thought it would be best to test the verification process first on two test machines before proceeding. The first run of the script came back fine saying that it had found the file on the one and the other one it initiated the sync then found the file. I added in more functionality to the script and fired that one off. In the logs I could see that the updated script had failed due to some fat fingering on my part with the directory locations. After fixing the directory locations I fired the script again just to have it hang out in limbo. The logs say that the script has pushed and it is waiting on either a success of a fail, but I checked the local directory for the script on the test machine just to see an empty folder. Does anyone know how to cancel the attempts that are not doing anything?
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
EdT
10 years ago
Use task manager to kill the process.
Comments:
-
Thanks for replying to my question, but I am not too worried about the client side of things as the scripts are not even showing up there. The Kbox run now status tab is just showing scripts that are pushed and are running, but they are not even reaching the client at all. I just want to make sure this isn't being lost in the network somehow or clogging up the Kbox. - Jhogue 10 years ago
-
Perhaps if you were to graphically show how you are setting things up, it may then become obvious where the problem lies. - EdT 10 years ago