Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 28 Oct 2003 10:56:21 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 1.5.5-1: fprintf(stdout, ...) writes to serial port when used by apcupsd Message-ID: <20031028155621.GA29657@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20031028031312 DOT GA9238 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Tue, Oct 28, 2003 at 10:27:23AM +0100, Alexander Schremmer wrote: >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 ... The author is wrong. It happens. You can probably get the same behavior from: #!/bin/sh exec 0<&- 1>&- apcupsd >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. Why don't you verify this for yourself rather than ask for corroboration from people who have never used the program? There is no magic here. -- 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/