Hey list, I've got a (presumably) unusual setup where I'm daemonising a Python script with supervisor, and that script then starts an X session with xinit (based on an external trigger).
The python script calls "/etc/init.d/xbmc start" via Popen. The command in the init.d script is then: /sbin/start-stop-daemon --start -c mafro --background --pidfile /var/run/xbmc/xbmc.pid --make-pidfile --exec /usr/bin/xinit -- /usr/local/bin/xbmc --standalone -- :0 This command runs fine in a TTY, but when daemonised in supervisor, I see the xinit process like this in ps: mafro 31019 31017 0 09:29 ? 00:00:00 [xinit] <defunct> Can anyone shed any light on what's happening here? Presumably there's some disparity between what xinit needs to start, and how supervisor manages it's child processes. Here's the supervisor config for completeness: [program:python-xbmc-start] directory=/srv/xbmc-start/ command=/home/mafro/.virtualenvs/xbmc-start/bin/python -u /srv/xbmc-start/script.py environment=PATH="/home/mafro/.virtualenvs/xbmc-start/bin" user=mafro autostart=true autorestart=true stdout_logfile=/var/log/mafro/xbmc-start/supervisor.log redirect_stderr=true Any input greatly appreciated. Thank you
_______________________________________________ Supervisor-users mailing list [email protected] https://lists.supervisord.org/mailman/listinfo/supervisor-users
