Problems interpreting errno

Matt Berney mberney@polyserve.com
Tue Mar 25 08:40:00 GMT 2003


Unfortunately, yes.  I had considered this option.  But, it would require changes to both the server and client-side code, that I was hoping to avoid.  

-----Original Message-----
From: Igor Pechtchanski [mailto:pechtcha@cs.nyu.edu]
Sent: Monday, March 24, 2003 7:31 PM
To: Matt Berney
Cc: cygwin@cygwin.com
Subject: Re: Problems interpreting errno


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@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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/



More information about the Cygwin mailing list