Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Alexander Schremmer" <alex AT alexanderweb DOT de>
To: <cygwin AT cygwin DOT com>
Subject: RE: 1.5.5-1: fprintf(stdout, ...) writes to serial port when used by apcupsd
Date: Tue, 28 Oct 2003 10:27:23 +0100
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAoJt1vBbz40CDAg5sGRmjl8KAAAAQAAAAvgx1VnOX2UOsmIeuQDl05QEAAAAA@alexanderweb.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <20031028031312.GA9238@redhat.com>

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/