one easy way to solve this would be have "nohup process_B.ksh" as the last line in process_A.ksh.
however, this is for a automation/scheduler piece that i am trying to write and process_A is any system user's process, while process_B is a sort of cleanup process done by the scheduler module. in the interest of keeping things unchanged for the eventual users - i don't want users to have to modify all their "process_A"s to include a line for process_B.
just in case, someone came up with the above solution
I am a little worried about this. The parentheses create a subshell and the ampersand puts this subshell into the background. The subshell then uses nohup to run the first process and then it uses nohup to run the second process. The problem is that the subshell itself is not nohup'ed.
I think that
nohup sh -c "( A ; B )" &
will avoid this problem.