This is the mail archive of the cygwin@cygwin.com 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: console output problem


Hi Igor - 
Thanks for the response.
I didn't redirect stdin but why would I need to? I just want to redirect
stdout and stderr to a log file. Stdin should come from the console but
there is no console input (unless args to applications are stdin). 
You're suggesting I redirect stdin to /dev/null? Would this work in
windows? What would be the effect? 


Thanks.
Jim


-----Original Message-----
From: Igor Pechtchanski [mailto:pechtcha@cs.nyu.edu] 
Sent: Friday, October 25, 2002 6:21 AM
To: Jim Rainville
Cc: cygwin@cygwin.com
Subject: Re: console output problem

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/


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