Hi, I struggled with this for a long time in the past. Turned out it needs a little time after creating the screen socket in order to start executing commands on that session. Otherwise it ends up saying there's no such session and halting the whole script (this is always reproducible). I solved it like this: --- /usr/gentoo/PORTDIR/app-emulation/xen-tools/files/xendomains.initd-r1 2009-09-01 06:56:36.000000000 -0300 +++ /etc/init.d/xendomains 2011-08-02 12:58:41.597559633 -0300 @@ -38,7 +38,7 @@ einfo "Starting Xen domains from ${AUTODIR:=/etc/xen/auto}" if using_screen ; then ebegin "Creating screen session to hold domain consoles" - ( screen -c ${SCREENRC:-/dev/null} -d -m -S ${SCREEN_NAME} -t dom0 \ + ( screen -c ${SCREENRC:-/dev/null} -d -m -S ${SCREEN_NAME} -t dom0 && sleep 3 \ && ${screen_cmd} zombie dr \ && logrotate -f /etc/xen/xen-consoles.logrotate \ && ${screen_cmd} logfile /var/log/xen-consoles/%t.log \ That kept my systems going all this time. I had this problem since always and *always* forgot to report it with the corresponding solution (which I tested a lot). Thanks.
Created attachment 289643 [details, diff] full patch for cvs
Fixed in tree
