Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <5.1.0.14.2.20010605163300.02524120@pop3.cris.com> X-Sender: rrschulz AT pop3 DOT cris DOT com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 05 Jun 2001 16:37:36 -0700 To: "Ting Chong Ma" , cygwin AT cygwin DOT com From: Randall R Schulz Subject: Re: bash 2.0.5 - Broken pipe for -h large number In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Hi, You should be aware that the "Broken pipe" message is just BASH reporting to you which signal (it was told) caused the termination of the program. SIGPIPE is sent to programs for a variety of reasons, usually when the gist of the error condition is that something sent by the program (to or via a pipe, socket or other IPC mechanism) could not be delivered, typically because the intended recipient is no longer around to receive it. In any event, it seems unlikely that this is a BASH or even a Cygwin problem. Perhaps the number (60000 vs. 200000) must fit in a 16-bit integer, and failing that some error condition was raised? Randall Schulz Mountain View, CA USA At 10:51 2001-06-05, Ting Chong Ma wrote: >bash 2.0.5 under NT 4.0 SP6A >I have written a windows console program called sendalarm.exe >and it accepts -h as an option. >The bash shell does not support a large number for the -h option >e.g. this is OK: >bash-2.05$ sendalarm -A tcma1 -n 91 -s M -h 60000 > >but this fail: >bash-2.05$ sendalarm -A tcma1 -n 91 -s M -h 200000 >Broken pipe -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple