Date: Mon, 06 Oct 2008 23:12:57 -0400
From: "EMF" <emf AT amhran DOT net>
Subject: RE: Terminal Services session hung: csrss.exe doesn't exit if  Cygwin  was run in the session
In-reply-to: <000201c927ce$3afc4f90$9601a8c0@CAM.ARTIMI.COM>
To: <cygwin AT cygwin DOT com>
Message-id: <004901c9282a$999f4820$0301a8c0@lambda>
MIME-version: 1.0
Content-type: multipart/mixed;  boundary="----=_NextPart_000_004A_01C92809.12901920"
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

------=_NextPart_000_004A_01C92809.12901920
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

What I guess I didn't explain clearly was that the MakeShare.sh script is
only on the 64-bit box.=20=20

I'll double-check tomorrow on the 64-bit box by commenting out all the
non-cygwin-"native" commands, but your query incites curiosity:  should I be
calling Win32/Win64 binaries in a different (indirect?) manner from within
bash?  (Did I miss something in the docs?)

The 32-bit box has hung in exactly the same way using scripts that use only
cygwin-"native" binaries from packages like OpenSSH and Cygwin/X.  I've
attached that script here, which I run from a Windows shortcut that has a
command line of:
	"Y:\Program Files\cygwin\bin\run.exe" /bin/bash --login -c
"/usr/local/bin/LaunchX.sh"


-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of
Dave Korn
Sent: Monday, October 06, 2008 12:12 PM
To: cygwin AT cygwin DOT com
Subject: RE: Terminal Services session hung: csrss.exe doesn't exit if
Cygwin was run in the session

EMF wrote on 05 October 2008 05:54:

> Is there anything else I can (or should have) provide(d) to help
> troubleshoot this?

  Well, the obvious test would be:

> I've encountered an issue running on Windows Server 2003,
> both 32-bit and 64-bit.  I can log in and out of Terminal
> Services sessions all day long if I don't start Cygwin,
> but if I start Cygwin and run, for example, the attached
> script (MakeShare.sh), then csrss.exe will hang when I log
> out, locking up the TS connection.

  What happens if you either don't run the script, or run the script but
comment out the two lines that invoke "bemcmd.exe"?

    cheers,
      DaveK
--=20
Can't think of a witty .sigline today....


--
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/

------=_NextPart_000_004A_01C92809.12901920
Content-Type: application/octet-stream;
	name="LaunchX.sh"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="LaunchX.sh"

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fcharset0 Couri=
er New;}{\f1\fswiss\fcharset0 Arial;}}
{\*\generator Msftedit 5.41.15.1507;}\viewkind4\uc1\pard\f0\fs20 #!/bin/bas=
h\par
\par
echo "Starting X..."\par
echo "(Minimize, but do not close this window until the session is complete=
.)"\par
\par
COUNTER=3D1\par
umask 077\par
while [ $COUNTER -lt 10 ]\par
do\par
\tab LOCKFILE=3D/tmp/.X11-unix/X$COUNTER\par
      if [ `ls $LOCKFILE 2>/dev/null | wc -l` -eq 0 ]\par
      then\par
\tab\tab /usr/X11R6/bin/xinit /usr/bin/xterm -display :$\{COUNTER\} $* 2>/d=
ev/null -- -multiwindow -logfile ~/X.log :$COUNTER\par
            exit 0\par
      else\par
              (( COUNTER =3D COUNTER + 1 ))\par
      fi\par
done\par
echo "Error: Could not find available screen."\par
sleep 5\f1\par
}
=00

------=_NextPart_000_004A_01C92809.12901920
Content-Type: text/plain; charset=us-ascii

--
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/
------=_NextPart_000_004A_01C92809.12901920--