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-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: Problems interpreting errno Date: Mon, 24 Mar 2003 18:52:19 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Matt Berney" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h2P2qUJ07730 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 -- 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/