I have a script which does launch another application using nohup my_app &
, but when the initial script dies the launched process also goes down. As per my understanding since since it has been ran with nohup
that should not happen. The original script also called with nohup.
What went wrong there?
A very reliable script that has been used successfully for years, and has always terminated after invoking a nohup uses this construct:
nohup ${BinDir}/${Watcher} >${DataDir}/${Watcher}.nohup.out 2>&1 &
Perhaps the problem is that output is not being managed?