RE: 1.5.x: Windows 2003 - no console output

["Igor Kalders" <igor at wefocus dot com>]

> Having the GnuWin32 tools in your path could be a source of confusion,
> so I wouldn't recommend that.  But it appears that your cygwin bin
> directory is first in the path and so the cygwin versions should be
> found.

Stripped it from the PATH. No change.


> But do note - by default \cygwin\bin is not added to the system path, it
> is only set by cygwin.bat when you click on the shortcut.  This means
> that if you did not manipulate the path otherwise, that \cygwin\bin will
> not be in the path when you just start CMD.EXE, and so there's a chance
> that you're still calling the GnuWin32 ls and bash in that case.  Your
> cygcheck shows \cygwin\bin in the path but if you ran this from the
> cygwin.bat shortcut then it doesn't necessarily tell us about your path
> environment in a regular CMD.EXE prompt.

Funny you mention that. I either do a "SET PATH=C:\cygwin\bin;%PATH%" within
my cmd or include the cygwin path in the Windows Environment.


> So, you start CMD.EXE and type "ls" and something runs but you see no
> output?  Does it hang, or just exit immediately?

1. I call CMD.exe
2. If not already in the PATH, I add C:\cygwin\bin (as the first entry)
3. If asked for, I adjust CYGWIN ;)
4. I call any command (bash, ls, true, ...)
5. The command seems to start up
6. The command shuts down without any output
7. The %ERRORLEVEL% is 128

Whatever I do in step 2 and 3, it changes nothing.


> What about when you
> open a bash prompt using the cygwin.bat shortcut and type "ls", does
> that work?  Does removing "tty" from $CYGWIN make any difference?  (By
> the way, "binmode" and "ntsec" are both on by default, so setting them
> in $CYGWIN essentially has no effect.)

That was what I did first, before I started digging. The bash prompt even
doesn't pop up. For your clear view: If I double-click the batch in Windows,
a cms.exe console windows pops up and goes away. So it looks like the
command really gets invoked. But invoking bash by double-clicking
cygwin.bat, is not any different from manually starting cmd.exe and calling
bash.

Also, adjusting CYGWIN within the batch makes no difference.

Since this wouldn't be the first time that I've been bugtracking for days
something that could be resolved by a restart, I restarted the (production!)
server yesterday. Also made no difference.

One more thing, I used FileMon to check for any files that are searched for
but not found. While executing e.g. ls, I found that SECUR32.DLL was sought
for in the cygwin/bin dir. I was not sure this was done by the cygwin
command, but I put it in that place anyway. Again, nothing changed. After
closing FileMon, I was unable to do any further investigation, as the prog
will not start again (Access Denied).

I really don't know what else I can check or try. I could restart the server
(at the end of the day), and do some further FileMon actions.

This is giving me a severe headache.

Igor




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