Subj : Bash script To : Rick Smith From : Maurice Kinal Date : Sat Jun 19 2021 10:07 pm -={ 2021-06-19 22:07:57.627712523+00:00 }=- Hey Rick! RS> So If I make a script that performs something and then it calls RS> say another script, would the first script then pause until the RS> called side script completes? That is the normal behavior. RS> If not is there a way to make it wait to move forward until the RS> other one completes? -={ ':read !wait --help' starts }=- wait: wait [-fn] [-p var] [id ...] Wait for job completion and return exit status. Waits for each process identified by an ID, which may be a process ID or a job specification, and reports its termination status. If ID is not given, waits for all currently active child processes, and the return status is zero. If ID is a job specification, waits for all processes in that job's pipeline. If the -n option is supplied, waits for a single job from the list of IDs, or, if no IDs are supplied, for the next job to complete and returns its exit status. If the -p option is supplied, the process or job identifier of the job for which the exit status is returned is assigned to the variable VAR named by the option argument. The variable will be unset initially, before any assignment. This is useful only when the -n option is supplied. If the -f option is supplied, and job control is enabled, waits for the specified ID to terminate, instead of waiting for it to change status. Exit Status: Returns the status of the last ID; fails if ID is invalid or an invalid option is given, or if -n is supplied and the shell has no unwaited-for children. -={ ':read !wait --help' ends }=- Of course you only need to do this when the script is running parallel processes where the output from one is needed for another. Life is good, Maurice .... Ælc mann þe wisdom lufaþ biþ gesælig. Everyone who loves wisdom is blessed. --- GNU bash, version 5.1.8(1)-release (x86_64-motorshed-linux-gnu) * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001) .