Hi, Christopher Faylor wrote:
> This is not a cygwin problem. It is a problem with a program > that assumes that it has a valid stdout. It is perfectly > possible that a program can be started with no stdout, stdin, or stderr. The author said that it must a problem of cygwin ... Is it enough to call ftell(stdout) and check for != -1 to check for a valid stdout? Then I'd submit that patch to apcupsd. Kind regards, Alexander -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
