This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Curious behavior of CYGSERVER
"David A. Cobb" <superbiskit@cox.net> 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/