Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 18 Jan 2002 13:06:53 -0500 From: Alex BATKO To: cygwin AT cygwin DOT com Subject: Re: no output from net.exe Message-ID: <20020118130653.D786@cs.mcgill.ca> References: <20020117130429 DOT C17402 AT cs DOT mcgill DOT ca> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020118100433 DOT 00b277a0 AT mail DOT biapo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.1.0.14.2.20020118100433.00b277a0@mail.biapo.com>; from rotaiv@biapo.com on Fri, Jan 18, 2002 at 10:08:55AM -0500 +------------------- | Have you tried use tee? For example: | | $ net group /domain | tee group.txt | This didn't help because I wasn't getting anything on stdout to begin with, and tee copies stdout to a file. So all i got was: nothing on the screen, and a file of size 0, called group.txt. But after setting the system (environment) variable CYGWIN to 'tty', as suggested by Peter Buckley, both net.exe (on it's own), as well as with a pipe to tee now work as expected. Thanks for your input. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/