This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: CreateFileMapping problem but Win32 error is 0

On Jul 18 22:41, Andrew DeFaria wrote:
> I am helping a client install a new server and we use a process that 
> essentially does an rsh <machine> make. The make process is fairly 
> complicated. The new server is a Windows 2003 Server. There is no RDP 
> involved - just an rsh. I'm getting errors like:
>      3 [main] bash 14596 C:\cygwin\bin\bash.exe: *** fatal error - 
> C:\cygwin\bin\bash.exe: *** CreateFileMapping 
> Global\cygwin1S4.cygpid.4648, Win32 error 0. 
> I've seen some posts regarding an error similar to this but it usually 
> involves and RDP session and an error code of 5 but here I have no RDP 
> session and the error code is strangely 0.
> The other thing that is odd is that in the process of make some of the 
> compilations will fail as the above and others won't. IOW it's 
> intermittent. Also it's not always bash that dies. Sometimes it's make:
>      4 [main] make (11352) C:\cygwin\bin\make.exe: *** fatal error - 
> C:   bin\make.exe: *** CreateFileMapping Global\cygwin1S4.cygpid.11352, 
> Win32   .  Terminating.
> Since the return code is 0 the make continues onward obliviously.
> Another interesting aspect is that if the user who is rsh'ing is added 
> to the local Administrators group then all these errors disappear.
> Note that people have passwordless rsh access to the server.

This is probably the problem.  I just wrote a lengthy explanation of
what happens in case of public key authentication, see:

You're getting the same problem in case of rhosts authentication, it
all boils down to "password-less authentication".

Your case is not exactly related but it doesn't hurt to read this first,
just to get an impression and maybe a coffee break.

I can't explain the error code 0 right now, but I assume your problem is
the handling of user rights related to global objects.  Reading
gives a bit of insight into the general problem.

I have to be able to reproduce the problem, which I can't ATM.
As a workaround try giving the "Create global objects" user right
to the sshd_server account alone.  If that doesn't work, add the
"Create global objects" right to the users login in through rsh.
Please report back the results of both tests.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]