This was a real bummer for me too, and none of the follow-up
suggestions met my needs, which is to have a clickable icon in Windows
that would open an x-term, starting the X server if necessary and not
complaining if one has already been started.
Scripting in Windows is a pain, but I finally
Running it as a service basically does not require starting, or
attempting to start, an Xserver each time you open a window. The
service runs continually in the background and listens for connections.
The procedure is relatively simple:
Create an environment variable:
CYGWIN = server
From a
http://cygwin.com/acronyms/#TOFU. Reformatted.
Randy Brown wrote:
Sergei Pachkov wrote:
Can you shortly describe start xserver as service?
Running it as a service basically does not require starting, or
attempting to start, an Xserver each time you open a window. The
service runs
Run the xserver as a Windows Service. That fixed it for us. Didn't fix
it, but eliminated the error. ;)
Randy
David Weintraub wrote:
I've been using Cygwin/X for several years, and I never had this
problem before. However, I've recently installed Cygwin/X on my new
system, and now I notice
I've been using Cygwin/X for several years, and I never had this
problem before. However, I've recently installed Cygwin/X on my new
system, and now I notice that XWin's -silent-dup-error command line
parameter no longer seems to work.
I startup Cygwin/X by creating a Windows shortcut that runs
Thanks. That actually makes a lot more sense than running XWin
multiple times each time I want an XTerm.
Not too sure how to start xserver as a Windows service, though. It's
not already listed as a Windows service, so I assume that this is
something I have to setup. Is the process documented
