This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: console output problem
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Jim Rainville <jrainville at valosystems dot com>
- Cc: cygwin at cygwin dot com
- Date: Fri, 25 Oct 2002 09:21:13 -0400 (EDT)
- Subject: Re: console output problem
- Reply-to: cygwin at cygwin dot com
On Fri, 25 Oct 2002, Jim Rainville wrote:
> Hi -
>
> I'm trying to set up a perl build script that runs every night, builds a
> bunch of code (using gcc) and saves the output to some log files. So I
> redirect stdout and stderr to some files and run the script that builds
> the load. This runs fine when I run it from the command prompt but when
> I run it from the windows scheduler I get a bunch of errors of the form:
>
> 0 [main] cpp 1001 fhandler_console::de_linearize: error opening
> console after exec, errno 13, Win32 error 5
> 0 [main] cc1 1002 fhandler_console::de_linearize: error opening
> console after exec, errno 13, Win32 error 5
> 0 [main] as 1003 fhandler_console::de_linearize: error opening
> console after exec, errno 13, Win32 error 5
> 0 [main] cpp 1001 fhandler_console::de_linearize: error opening
> console after exec, errno 13, Win32 error 5
> 0 [main] cc1 1002 fhandler_console::de_linearize: error opening
> console after exec, errno 13, Win32 error 5
> 0 [main] as 1003 fhandler_console::de_linearize: error opening
> console after exec, errno 13, Win32 error 5
>
> It looks like since the scheduler doesn't have a console associated with
> it the fhandler_console throws an error even though stdout is
> redirected. Has anybody come across this before? Any clues how to fix
> it?
>
> Thanks. Jim
Jim,
Did you also remember redirect stdin from /dev/null?
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Water molecules expand as they grow warmer" (C) Popular Science, Oct'02, p.51
--
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/