Problems interpreting errno

[Matt Berney]

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/