drunc-controller process sometimes does not get cleaned up

[bieryAtFnal]

Sometimes when I exit a drunc interactive session, a stale drunc-controller session is left behind that I need to kill by hand.

Here are sample steps to demonstrate this:

DATE_PREFIX=`date '+%d%b'`
TIME_SUFFIX=`date '+%H%M'`

source /cvmfs/dunedaq.opensciencegrid.org/setup_dunedaq.sh
setup_dbt latest_v5
dbt-create -n NFDT_DEV_240815_A9 ${DATE_PREFIX}FDv5Test_${TIME_SUFFIX}
cd ${DATE_PREFIX}FDv5Test_${TIME_SUFFIX}/sourcecode

git clone https://github.com/DUNE-DAQ/appmodel.git -b kbiery/second_session_example
git clone https://github.com/DUNE-DAQ/trgdataformats.git -b develop
git clone https://github.com/DUNE-DAQ/trigger.git -b develop
cd ..

dbt-workarea-env
dbt-build -j 12
dbt-workarea-env

mkdir rundir
cd rundir

# Execute the following commands by hand:

drunc-unified-shell ssh-standalone

# within drunc (NB the use of "swtest-session")

boot test/config/test-session.data.xml swtest-session
fsm conf
fsm start run_number 101
fsm enable_triggers
# wait for a few seconds
fsm disable_triggers
fsm drain_dataflow
fsm stop_trigger_sources
fsm stop
fsm scrap
exit

sleep 15
ps -fu $USER | grep drunc | grep -v grep

[PawelPlesniak]

I have duplicated this. In nanorc the processs get killed when spawning a new session, needs discussion for drunc

[plasorak]

@bieryAtFnal, a zombie processes bug was fixed last week by Pawel. I'll let you reopen if the problem is still there.