This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


Igor Kalders wrote:

> - Start the console with "C:\WINDOWS\system32\cmd.exe"
> - CD to the cygwin installation directory ("C:\Program Files\OpenSSH",
> "C:\Program Files\CopSSH" or "C:\cygwin")
> - Execute any command (ls, ps, man, bash, ...)
> - Getting no console output

You are running non-Cygwin programs in a Cygwin tty (because you have
'tty' in $CYGWIN.)  Non-Cygwin programs do not know what a Cygwin tty
is, and think they are writing to a pipe.  This causes the output to be
buffered, so you only see output in large chunks when the buffer fills
enough to be flushed.

The reason it works when you launch them from strace is because strace
is not a Cygwin binary (that is, it's compiled with mingw and doesn't
use cygwin1.dll) and so when it launches the child process a
normal/native console is used.

The solution is probably one of:

- Don't try to run non-Cygwin programs from a Cygwin tty.  Why in the
world are you not using the Cygwin-packaged openssh?  It will not suffer
from this.

- Remove 'tty' from $CYGWIN (and don't use rxvt/xterm) in which case
Cygwin will not use a pseudoterminal but instead use the native windows
console.

Brian

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]