Shell Programming and Scripting

The title sounds like an easy problem (maybe it is), however, the catch is that when a job 'A' is called inside a wrapper, the execution does not wait for 'A' to finish, but it goes on to the next line (right after kicking off 'A').

My question is, how will you keep the execution waiting for that job to complete, so that I can perform some cleanup and/or archiving of files after 'A' completes.

*Note: Something that might help.... When 'A' is kicked off, it begins writing some lines of data to a file called success.txt. When 'A' completes, it stops writing to success.txt.

Thanks,

CB

Not sure if this helps, but did you try executing task A using 'eval' command ?

Not sure if you already had a solution for this. I guess sleep command would help.After the execution command of job A , the next statement can be a sleep statement.Let job A finish completely and then you can go the next line.

No idea if you have time contraints , but if you don;t this could be tried.

sleep will put the current thread to sleep for ## seconds. However, each time the process runtime varies, so I cannot hard-code the number of seconds.

Is job A called in the background? Post the line of code that kicks off job A.