Am Sonntag, 21. M�rz 2004 14:01 schrieb Alexander Gottwald: > Volker Lenhardt wrote: > > But the X server stays running, its logo lingers in the systray. I have > > to shut it by a series of 3 clicks. No alt-f4. If I don't do so, I get > > another X server the next time I start my xsane batch. > > if you don't use mulitwindowmode or the clipboard you can add the option > -once to the commandline. the xserver will exit after the last client quit. >
I tried, but xsane is easier to be used in multiwindow mode. And the X server nonetheless has to be shut down explicitly after exiting xsane. > > There's some cleaning up mechanism at the start of startxwin.bat, but it > > doesn't seem to be helpful. How can I check for a running X server, so > > my batch doesn't start a new one? Or how can I close the X server at the > > close of the batch? > > I another xserver is already running then the newly started xserver will > notice it and not start up. > I'd be happy, if it did so. So I try and skip all of the cleaning up and start XWin only if there doesn't exist a .../tmp/X0. It works so far. Can I get into trouble some time if I don't clean up? Regards Volker -- Volker Lenhardt E-Mail: [EMAIL PROTECTED]
