Mail Archives: cygwin/2006/08/10/03:55:17
On Aug 7 17:56, a DOT heider AT gom DOT com wrote:
> hi,
>
> we have cygwin installed on a development windows server. os is windows
> server 2003 standard r2 x64, and users are logging in through opensshd and
> rdesktop. we're encountering this problem:
>
> 2 [main] bash (4544) C:\cygwin\bin\bash.exe: *** fatal error -
> C:\cygwin\bin\bash.exe: *** CreateFileMapping
> Global\cygwin1S4.cygpid.4544, Win32 error 0. Terminating.
I wonder what we can do against that. The error message is only
generated if CreateFileMapping returns a NULL handle and the Windows
error code is 0. Which means, there's no hint why CreateFileMapping
failed at all. I searched MSDN and the Windows Knowledge Base for this,
but to no avail. I also didn't find any hint in the net about this
scenario.
> it happens to all users to all kind of cygwin-processes (make, bash, sed,
> ...) at (as it seems) random times. it only happens to global mappings
> with error always set to zero and it seems to occur more often on more
> concurrent (multiuser) make instances. our make process spawns alot of
> additional processes. it doesnt matter if the user is logged in through
> sshd (openssh installed as a cygwin service) or rdesktop.
So, just to be sure about this. You're claiming that it happens when a
user already has logged on for a while, is running Cygwin for a while?
And then the above error just happens at one point? It does not happen
at the time the user tries to start his or her first Cygwin process?
Can you tell me if the users which are logging in through rdesktop
are Admins, or if they have the SeCreateGlobalPrivilege explicitely set?
In theory, normal non-Admin users logging in through rdesktop should
never create global objects, so they shouldn't see the above message.
> while digging through the mailinglist, i found two possible solutions:
> 1) rebase the whole cygwin installation
> 2) give the sshd/user more privileges (SeCreateGlobalPrivilege...)
>
> none of the above solved our problem. today 2 users got the exact same
> error message including the pid field. is there a possible conflict and
> users connected through terminal services can have identical
> (cygwin/windows) pids?
Pids are quickly reused in a Windows system, so the error doesn't
mean much, except you can prove that it happened at the same time.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -