(possible) bug: does boxxy work when original process fork() s and exit( ) s ?

[georgemarselis-nvi]

Hello,

galaxy is a bioinformatics processing server and workflow thingie. It runs on python's uwsgi .

The software has two modes : --daemon and foreground (when not run under apache/ngnix)

When running with --daemon, the original uwsgi process forks and exits , which undoes all the work boxxy has done.

here it is after starting with /opt/galaxy/bin/boxxy /opt/galaxy/21.09/run.sh --daemon

here it is after starting with /opt/galaxy/bin/boxxy /opt/galaxy/21.09/run.sh (stay in foreground)

pstree says that the environment should be boxxed

apologies if this a wrong ticket! this tool is gonna save a lot of headaches in HPC clusters, where the sysadmins either cannot change the app (cuz the original company just says "no") or the grad student has moved on after finishing their degree/postdoc