Jessee Parker wrote: > Honestly I'm stuck. If I kill the process after it does it's job, I'm > thinking that there is no residual from the previous program. When I do > a ps -A there is only 1 program left to kill after it finishes > processing. I kill this process and run my script. Whenever the 2nd run > occurs, it acts as if processing is taking place when it really isn't. I > know this because all the files are left in the database instead of > being cleared out. The only thing I can think of is that for some reason > the variables on the 2nd run are not being passed. When I get to work > tomorrow, I will put in print statements to see if this is indeed the > case. Why it would work the first time through and not the next time > through (after being killed) has got me stumped. Any ideals? >
yes and i have seen it happened before especially your proces involves DBMS. i don't know what DBMS you are using(you might have tell us but i forget) but is it possible that when you kill your process, your DBMS is left in a corrupted state? did you end up using transaction? did you roll everyting back when you kill your process? or commit it? if you kill your process and your DBMS is doing something in that time, it might left in a corrupted state so your second run won't be successful. here is a real life example from one of my friend. he's working in windos and have a script that updates an Access DB (if you can call Access a real DB :-), when he started the process, he quickly notice something is wrong so he ^C-ed the script. After he fixed what he think is wrong, he runs the scritp again but it never success. he found out that when he killed the script, Access didn't have time to clean up the lock file so the second run keep complain about the Access DB is open by another process and refuse to run again. i seldom work in windos and don't know much about Access but i hope you get what i mean... you probably want to check similiar stuff and see if it's possible that the first run (after you kill the process) is corrupting the DBMS so your future runs won't be succecssful. david -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
