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 Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <013601c25ce9$498fee60$6132bc3e@BABEL> From: "Conrad Scott" To: "Cygwin Discussion" References: <3D83E5C6 DOT 90102 AT cox DOT net> <00a901c25c9d$49580000$6132bc3e AT BABEL> <3D84CFAF DOT 40103 AT cox DOT net> Subject: Re: Curious behavior of CYGSERVER Date: Sun, 15 Sep 2002 19:54:14 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 "David A. Cobb" wrote: > > Conrad Scott wrote: > > > > This I don't understand and cannot recreate any such problem. That is, > > with cygserver running, redirection of both stdout and stderr work fine > > in my little tests. Could you give more detail on exactly how stdout > > redirection is "defeated"? > > I have my configure, make-bootstrap, make-check bundled in a single > "build.sh" script. If I do either: > > $ source ./build.sh >build.log 2>&1; or > $ ./build.sh >build.log 2>&1 > > It goes merrily along but, when all is said and done, "build.log" don't > exist. Not even somehow misplaced - I searched my whole darn machine. > > I also did a $ find ..... >found-files.txt and had the same result (no > output file) Which shell are you using? And couldI see the output from `cygcheck -s -v -r'? Thanks. > WAIT A MO', I > cleaned up /tmp yesterday before one run and the Windows exception came > back even with Cygserver active. Check my other thread about that. So, cygserver is not related to *that* issue then. That simplifies things a bit :-) Cheers, // Conrad -- 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/