Dave: : Hmmm, one of those is a login shell, and the other is not. That may well : make the difference. If you add the "-ls" option to the xterm invocation, : does it then behave the same as when you start via cygwin.bat?
This makes no difference. I still get the reported errors. : It isn't anything to do with X; it's to do with the way the environment is : configured. And probably the underlying problem with your service (as : illustrated by the two separate ways of invoking shells above) is that the : environment isn't set right. : : Take a look at the difference in your cygcheck output between the sshd : config and the cygserver config; I think you need to specify CYGWIN=server in : the environment for that particular service, not in your per-user windows : environment. : : So try re-running the cygrunsrv command you used to set up cygserver, and : this time add the option "-e CYGWIN=server". See this section of the docs for : an example: : : http://cygwin.com/cygwin-ug-net/using-cygserver.html#use-cygserver In this doc, I have followed the first prescription, setting CYGWIN to server in my Windows environment. (If so I shouldn't even need to add `set CYGWIN=server` in cygwin.bat. Isn't this correct?). Therefore, I should not have to use `cygrunsrv -I foo -p /usr/sbin/foo -e "CYGWIN=server"` Isn't this correct? In any case I am not sure what "service" to implement here to replace "foo"? I did try adding `set CYGWIN=server` in my startupx.sh, but I still get the same errors. Thanks. Lester -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
