Hi Pierre,
thanks first for looking at my problem!
Regarding the CreateFileMapping problem, the message you report is
*** CreateFileMapping, Win32 error 0. Terminating.
but the code in Cygwin is
api_fatal (CreateFileMapping %s, %E. Terminating., mapname);
The *** in front is added
Dave Korn wrote:
another question to this topic came into my mind:
why is this all happening only to the Windows Server 2003 machine?
Ah, but then you go and point out that...
Although the SAMBA problem appears on all machines.
That's true. It seems that I have two problems here and the
Thanks a lot to all who helped me.
In case one encounters this problem the web-site:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dncode/html/secure06122003.asp
gives an answer.
Creating Various Global Objects May Fail:
Starting with Windows Server 2003, the creation of
Thank you all for your help!
the 'global object privilege' was the reason for
cygwin not running on the Win2003 Server.
As a matter of fact. The original question
started in another thread first and moved to
this one due to two seperate problems.
Do they have the create global object privilege?
Sorry Pierre,
I replied to your personal address only, but it was bouncing back.
uname -r says 1.5.5(0.94/3/2)
when I have cygwin installed and update via setup, what I
definitely did, why do I have an older version than expected?
I thought it must be the latest version that I have.
Stefan
Now I have version 1.5.6(0.108/3/2).
When was this one released?
Shall I revert the privilege stuff to test again?
Stefan
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
, 2004 at 03:55:44PM +0100, Stefan Zachow wrote:
Now I have version 1.5.6(0.108/3/2).
When was this one released?
Shall I revert the privilege stuff to test again?
Yes please.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com
Good morning,
How about when you start bash from a command prompt (i.e., open an MS DOS
prompt window, cd c:\cygwin\bin, and .\bash.exe --login -i) as a
non-administrative user? What if you omit --login?
when I enter .\bash.exe --login -i (with or without --login) I get
*** CreateFileMapping,
Further info...
'mkgroup' is strange. It seems that I cannot synchronize with
our network databases. A mkgroup -u -d DOMAIN gives the
following two lines of output:
LookupAccountName (\\Host, Domain Admins) failed with error 1332
LookupAccountName (\\Host, Domain Users) failed with error 1332
Dear cygwin experts,
I encountered some problems with the mkgroup command during
my trial to get cygwin running on a Windows 2003 server machine
(Topic: running the latest cygwin on a windows 2003 server)
The domain controller is a Linux system running Samba for file
system sharing.
The 'mkpasswd
Dave Korn wrote:
Try giving your cygwin non-admin user accounts the Create paging files
privilege and see if that helps. I _think_ you have to do that using the
group policy editor, gpedit.msc.
OK, I did - unfortunately without any change.
How is this Windows information mapped
to cygwin, resp.
Dear Corinna,
although I won't get the group information, it must
be possible to create one manually. What is the
typical syntax of the group info returned by
mkgroup -d DOMAIN?
I could try adding that stuff since I cannot persuade
our domain controller to answer correctly.
Setting up a new Samba
Sorry, I forgot to ask:
what are the default permissions and user/group combinations
after cygwin install?
I have administrator/mkpasswd with access code 750
over the entire cygwin tree.
Should I simply change the group to somethin like 'Users'?
Stefan
--
Unsubscribe info:
another question to this topic came into my mind:
why is this all happening only to the Windows Server 2003 machine?
The same installation with the same configuration runs well with
Windows 2000 or Windows XP. Although the SAMBA problem
appears on all machines. It must have something to do with
Dear cygwin experts,
I went through the mailing list archive searching for
windows 2003 server but the resulting 10 pages
didn't really help.
Could anybody please provide a hint to my problem
running cygwin on a Windows 2003 server?
I can only start a cygnus shell when I am a member
of the
Larry,
Also, who did you install Cygwin as and did you install it for All users
or Just me? The answer to the last part may provide you with the answer
you seek. Otherwise, please provide more specific information as requested
above.
I did install cygwin as Administrator for 'all users'.
Since
Igor,
What is the exact message you get when you try to run Cygwin programs as
another user? Which exact programs fail? Do all the programs fail in
the
same way?
Unfortunetly users that are not in the administrator group cannot even start
a bash. That's why I took an Administrative user to
17 matches
Mail list logo
