Passing errno values across systems isn't portable. You need to define
your own error codes and map errno to those. There is nothing else you
can do if you want to be portable.
These problems pop up in various networked file systems every once in a
while. The most recent one I saw was on AFS wh
On Mon, Mar 24, 2003 at 09:12:59PM -0800, Matt Berney wrote:
> 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.
I don't see another chance. Numerical errno values are nonportable.
Corinna
PROTECTED]
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 re
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
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
5 matches
Mail list logo
