Excerpts from Antoine Martin's message of Thu Jul 12 08:00:06 +0200 2012: > On 11/07/12 00:21, Michal Suchanek wrote: > > Excerpts from Antoine Martin's message of Tue Jul 10 17:11:02 +0200 2012:
> > Note also that the true command exits immediately so any dbus, > > ssh-agent, and similar daemons started by the session will exit > > immediately as well. > > > > You could run a non-ending process instead but then the session daemons > > would stay even after the X server exits. > > > > A client that connects to the X server and waits for it to terminate > > would be ideal but I know of none that does just this. > Odd, because it would be trivial to write. It is not the most trivial, you need to process X events so that you notice the connection error when the X server goes away. Or watch the fd if you can extort Xlib to give you the fd of the server connection. > > > Perhaps some sample script in documentation, or perhaps even a > > xorg.conf.dummy and a script in /usr/bin using it could be installed > > with xpra so that everyone does not have to figure out how the hell is > > that thing supposed to work. > > > > A sample script using xorg.conf.dummy could look like this: > > > > xpra --xvfb="Xorg -nolisten tcp -config xorg.conf.dummy -noreset +extension > > GLX +extension RANDR +extension RENDER -logfile > > ~/.xpra/xserver-$DISPLAY.log" --start-child="/etc/X11/Xsession true" start > > :$DISPLAY > > > > It is sad that you can't know what display xpra picks when starting it > > but without actually patching xpra you can't do more than that. > I think the config file option above is the easiest way to improve > things quickly? It requires that the xorg.conf linked on the wiki is installed at /etc/X11/xorg.conf.dummy Otherwise full path to the file is required. Thanks Michal -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
