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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Mon, 24 Mar 2003 22:31:26 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Matt Berney cc: cygwin AT cygwin DOT com Subject: Re: Problems interpreting errno In-Reply-To: Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 24 Mar 2003, Matt Berney wrote: > I have a client/server application that runs the client on a Linux > workstation (RHAS) and runs the server on Win2k (under Cygwin). The > client sends a filesystem command to the server and returns the errno. > Here is the problem.... > > The file system call on Win2k (under cygwin) generates the errno, but > the text string for the errno is interpreted on the client-side (under > Linux), using the strerror() function. As a result, the error message > is mis-interpreted. > > For example, > Win2k ENOEMPTY = 90 > Linux EMSGSIZE = 90 > > In other words, the error that occurred was "Directory not empty", but > the text displayed by the client was "Message too long". > > Any ideas how to resolve the discrepency? > > Thanks, > Matt Berney You mean, aside from the obvious "interpret the error on the server and send a string to the client"? ;-) Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk! -- /usr/games/fortune -- 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/