Re: running the latest cygwin on a windows 2003 server
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 SAMBA thing is _not_ the one that hinders cygwin to run, right? And you're using a domain, right? Yes in both cases. Is this related to the Pre-Windows 2000 Compatible Access group thingy? As a matter of fact I don't have any clue. I have to read this first http://www.google.com/search?hl=enlr=ie=UTF-8oe=UTF-8q=pre-windows+2000+ compatible+access+group but your former advice seems setting me on the track. I only have to figure out how to do set global priviliges You might both find some useful information in this article Development Impacts of Security Changes in Windows Server 2003: http://msdn.microsoft.com/library/en-us/dncode/html/secure06122003.asp Creating Various Global Objects May Fail : Starting with Windows Server 2003, the creation of some global objects, such as file mapping will fail unless the calling process has the SeCreateGlobalPrivilege privilege enabled. Note that the privilege check is limited to the creating of said objects, and does not apply to opening existing ones. For example, the following code will fail on Windows Server 2003 unless the process account has this privilege: HANDLE hMap = CreateFileMapping(INVALID_HANDLE_VALUE,0,PAGE_READWRITE, 0, 0x,Global\\MyMapping); By default this privilege is assigned to all services and administrators. This privilege also applies when creating symbolic links in the object manager. The way around this is to either grant the account in question this privilege, or do not make the object name global. Of course, the latter may not be possible. Regards, Stefan -- 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/
Re: running the latest cygwin on a windows 2003 server
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 some global objects, such as file mapping will fail unless the calling process has the SeCreateGlobalPrivilege privilege enabled. Note that the privilege check is limited to the creating of said objects, and does not apply to opening existing ones. For example, the following code will fail on Windows Server 2003 unless the process account has this privilege: HANDLE hMap = CreateFileMapping(INVALID_HANDLE_VALUE,0,PAGE_READWRITE, 0, 0x,Global\\MyMapping); By default this privilege is assigned to all services and administrators. This privilege also applies when creating symbolic links in the object manager. The way around this is to either grant the account in question this privilege, or do not make the object name global. Of course, the latter may not be possible. OK now, how to solve this: Start - Administrative Tools - Local Security Policy Security Settings - Local Policies - User Rights Assignment Key: Create Global Objects Add the group that has limited rights (e.g. Remote Desktor Users) Stefan -- 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/
Re: running the latest cygwin on a windows 2003 server
On Thu, 22 Jan 2004, Stefan Zachow wrote: [snip] I only have to figure out how to do set global priviliges Stefan, Did you try the editrights tool? Grab it using Cygwin's setup.exe. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- 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/
Re: running the latest cygwin on a windows 2003 server
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, Win32 error 0. Terminating. This may not have worked with nontsec. Also, any particular reason you used X instead of x? What is the default after installation? I assume that I set the cygwin environment variable afterwards. However, now it is ntsec again according to your advice. I used chmod -R o+rX in the cygwin root to open any directory and chmod 755 in bin and /usr/bin. I didn't want to make everything executable. Hmm, maybe Pierre or Corinna can voice an opinion on this one. I don't know very much about Samba but is it possible to have a problem there? User and group related stuff is mapped on our Samba Server which is a Linux box. I don't know the Samba version right now, but it is not the latest one. Maybe anybody knows about that. What does ls -l /bin/bash under an administrative account show? How about getfacl /bin/bash? -rwxr-xr-x+ 1 administ mkgroup- 527360 Oct 20 14:12 /bin/bash.exe # file: /bin/bash # ownder: administrator # group: mkgroup-l-d user::rwx group::r-x group:SYSTEM:rwx group:Administrators:rwx group:Remote Desktop Users:r-x mask:rwx other:r-x Anyway, your help is greatly appreciated. Thanks a lot! Stefan -- 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/
Re: running the latest cygwin on a windows 2003 server
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 Hmm, maybe Pierre or Corinna can voice an opinion on this one. 'mkpasswd -d DOMAIN' works fine. I get the output I need. Could anybody explain the different behaviour of mkpasswd and mkgroup? Is it possible that the missing group info has something to do with the problem that cygwin does not run on my Windows 2003 Server machine or should I open a new thread on this mkgroup problem? Stefan -- 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/
RE: running the latest cygwin on a windows 2003 server
-Original Message- From: cygwin-owner On Behalf Of Stefan Zachow when I enter .\bash.exe --login -i (with or without --login) I get *** CreateFileMapping, Win32 error 0. Terminating. Fascinating. That's from winsup\cygwin\shared.cc line 96. Can't see why it would fail without returning an error code, though. 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. If that fixes the problem, then it would be worth adopting a more systematic method for your longterm solution. Probably the most 'correct' way to do it would be by creating a new group called Cygwin Users, using the control panel / (local) user and groups settings. Then you'd start gpedit.msc, follow the chain Computer configuration - Windows settings - Security settings - Local Policies - User Rights Assignment, find the 'Create a pagefile' option, and add the new Cygwin Users group to that. That way you can just add the users who need Cygwin access to the Cygwin Users group, and it'll give them the added privilege they need. cheers, DaveK -- Can't think of a witty .sigline today -- 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/
Re: running the latest cygwin on a windows 2003 server
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. how do I synchronize this with my group settings in /etc/group ? I did rebuild /etc/group again for local groups? With 'mkgroup- d DOMAIN' I have some other problems, sigh. The problem occurs only for non local users, mapped into the system via mkpasswd -d DOMAIN and mkgroup -D DOMAIN Since my user information is comming from a domain database I cannot assign the 'cygwin users' group to all possible users, neither I can add them all as local users. What else do I have to consider after changing the 'create pagefile' option? Stefan -- 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/
RE: running the latest cygwin on a windows 2003 server
-Original Message- From: Stefan Zachow 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. Ah, of course, you're using a domain. The enabled privs for domain users and groups come from the domain controller, rather than the local machine. So altering the privs locally isn't an option. D'oh, my bad. Secondly, I shouldn't have told you to use gpedit.msc; I should have told you to use the local security settings tool in the control panel/administrative tools. Double d'oh. However, all this is irrelevant anyway, since you're logged into a domain. How is this Windows information mapped to cygwin, resp. how do I synchronize this with my group settings in /etc/group ? It isn't mapped to cygwin. It's just that any logged-in user only has certain rights to access and use various of the OS facilities. If you're logged into your machine and you don't have the right to create paging files, then *any* program, not just cygwin, that tries to create one will fail. The information about which users are members of which groups is available to cygwin, and that's what the mkgroup command is for: it contacts the domain controller and finds out what groups there are in the domain and which users are in each group. For cygwin to know about the new cygwin users group, you'd need to regenerate your /etc/group file with mkgroup; but it doesn't matter in this case, because it is the underlying OS rather than cygwin that is responsible for enforcing the create paging file privilege. Note also that changes to your user/group privilege settings don't take effect until you logout and log back in again. Your access token needs rebuilding. I did rebuild /etc/group again for local groups? With 'mkgroup- d DOMAIN' I have some other problems, sigh. The problem occurs only for non local users, mapped into the system via mkpasswd -d DOMAIN and mkgroup -D DOMAIN Since my user information is comming from a domain database I cannot assign the 'cygwin users' group to all possible users, neither I can add them all as local users. Yep, because you're dealing with domain groups and users, none of the settings on the local machine affect the rights/privs those user accounts are granted. You'll have to try implementing this fix at the domain controller. What else do I have to consider after changing the 'create pagefile' option? You'll need the domain admin to create a group for Cygwin Users, to give the cygwin users the Create paging files right in the domain policies, and to add a non-admin user to that group for you just to test if this is really the problem. *OR*, and I'm not 100% sure this would work but it probably will, you could go to control panel/administrative tools/local security settings, go to Security settings/local policies/audit policy, double-click the 'audit privilege use' option, and enable both success and failure logging. Then you could retry starting bash, and see if an event turns up in the security event log; this would at least tell you whether or not the problem truly is that the non-admin users aren't allowed to create paging files. cheers, DaveK -- Can't think of a witty .sigline today -- 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/
Re: running the latest cygwin on a windows 2003 server
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 specific tools that run during setup and configure something wrong. 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, Win32 error 0. Terminating. Kind regards, Stefan -- 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/
Re: running the latest cygwin on a windows 2003 server
Stefan Zachow wrote: why is this all happening only to the Windows Server 2003 machine? Because Microsoft tightened down a lot of things in Win2K3 that previous Windows OSes allowed. I upgraded a server from Win2K to Win2K3 a few weeks ago, and already we've been bit by two of these paranoia changes. I don't yet have any experience that bears directly on your problem; this is just a general observation. -- 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/
RE: running the latest cygwin on a windows 2003 server
-Original Message- From: cygwin-owner On Behalf Of Warren Young Stefan Zachow wrote: why is this all happening only to the Windows Server 2003 machine? Because Microsoft tightened down a lot of things in Win2K3 that previous Windows OSes allowed. I upgraded a server from Win2K to Win2K3 a few weeks ago, and already we've been bit by two of these paranoia changes. I don't yet have any experience that bears directly on your problem; this is just a general observation. You might both find some useful information in this article Development Impacts of Security Changes in Windows Server 2003: http://msdn.microsoft.com/library/en-us/dncode/html/secure06122003.asp cheers, DaveK -- Can't think of a witty .sigline today -- 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/
Re: running the latest cygwin on a windows 2003 server
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 you gave me the link to http://cygwin.com/problems.html
I assume that I have to run 'cygcheck -s -v -r' to provide
more specific information. In case this is not what you meant
please let me know.
Stefan
8888888
Cygwin Win95/NT Configuration Diagnostics
Current System Time: Tue Jan 20 16:31:53 2004
Windows .NET Enterprise Server Ver 5.2 Build 3790
Path: C:\cygwin\usr\local\bin
C:\cygwin\bin
C:\cygwin\bin
C:\cygwin\usr\X11R6\bin
C:\cygwin\bin
c:\Perl\bin\
c:\WINDOWS\system32
c:\WINDOWS
c:\WINDOWS\System32\Wbem
c:\j2sdk1.4.2_02\bin
c:\Program Files\SSH Communications Security\SSH Secure Shell
Output from C:\cygwin\bin\id.exe (nontsec)
UID: 11300(administrator) GID: 10545(mkgroup-l-d)
10545(mkgroup-l-d)
Output from C:\cygwin\bin\id.exe (ntsec)
UID: 11300(administrator) GID: 10545(mkgroup-l-d)
544(Administrators)555(Remote Desktop Users)
545(Users) 10545(mkgroup-l-d)
SysDir: C:\WINDOWS\system32
WinDir: C:\Documents and Settings\administrator.VISUAL\WINDOWS
CYGWIN = `nontsec'
HOME = `c:\Documents and Settings\administrator.VISUAL'
MAKE_MODE = `unix'
PWD = `/cygdrive/c/tmp'
USER = `administrator'
ALLUSERSPROFILE = `C:\Documents and Settings\All Users'
APPDATA = `C:\Documents and Settings\administrator.VISUAL\Application Data'
CLIENTNAME = `QUINCE'
CLUSTERLOG = `C:\WINDOWS\Cluster\cluster.log'
COMMONPROGRAMFILES = `C:\Program Files\Common Files'
COMPUTERNAME = `TAMARIND'
COMSPEC = `C:\WINDOWS\system32\cmd.exe'
CVS_RSH = `/bin/ssh'
HOMEDRIVE = `C:'
HOMEPATH = `\Documents and Settings\administrator.VISUAL'
HOSTNAME = `tamarind'
INFOPATH =
`/usr/local/info:/usr/info:/usr/share/info:/usr/autotool/devel/info:/usr/autotool/stable/info:'
LOGONSERVER = `\\KIWI'
MANPATH =
`/usr/local/man:/usr/man:/usr/share/man:/usr/autotool/devel/man::/usr/X11R6/man:/usr/ssl/man'
NUMBER_OF_PROCESSORS = `2'
OLDPWD = `/cygdrive/c/tmp/cygwin_old'
OS = `Windows_NT'
PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
PKG_CONFIG_PATH = `:/usr/X11R6/lib/pkgconfig'
PROCESSOR_ARCHITECTURE = `x86'
PROCESSOR_IDENTIFIER = `x86 Family 15 Model 2 Stepping 7, GenuineIntel'
PROCESSOR_LEVEL = `15'
PROCESSOR_REVISION = `0207'
PROGRAMFILES = `C:\Program Files'
PROMPT = `$P$G'
PS1 = `\[\033]0;\w\007
[EMAIL PROTECTED] \[\033[33m\w\033[0m\]
$ '
SESSIONNAME = `RDP-Tcp#90'
SHLVL = `1'
SYSTEMDRIVE = `C:'
SYSTEMROOT = `C:\WINDOWS'
TEMP = `c:\DOCUME~1\ADMINI~1.VIS\LOCALS~1\Temp\4'
TERM = `cygwin'
TEXMF = `{/usr/share/lilypond/2.0.1,/usr/share/texmf}'
TMP = `c:\DOCUME~1\ADMINI~1.VIS\LOCALS~1\Temp\4'
USERDOMAIN = `VISUAL'
USERNAME = `administrator'
USERPROFILE = `C:\Documents and Settings\administrator.VISUAL'
WINDIR = `C:\WINDOWS'
_ = `/usr/bin/cygcheck'
HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
(default) = `/cygdrive'
cygdrive flags = 0x0020
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/
(default) = `C:\cygwin'
flags = 0x0008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/cygdrive/w
(default) = `\kiwiwinhome'
flags = 0x000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/cygrive/w
(default) = `\\kiwi\winhome'
flags = 0x010a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
(default) = `C:\cygwin/bin'
flags = 0x0008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
(default) = `C:\cygwin/lib'
flags = 0x0008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/X11R6/lib/X11/fonts
(default) = `C:\cygwin\usr\X11R6\lib\X11\fonts'
flags = 0x000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/w
(default) = `\\kiwi\winhome'
flags = 0x010a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal
Server\Install\Software\Cygnus Solutions
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal
Server\Install\Software\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal
Server\Install\Software\Cygnus Solutions\Cygwin\mounts v2
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal
Server\Install\Software\Cygnus
Re: running the latest cygwin on a windows 2003 server
On Tue, 20 Jan 2004, Stefan Zachow wrote: 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 you gave me the link to http://cygwin.com/problems.html I assume that I have to run 'cygcheck -s -v -r' to provide more specific information. In case this is not what you meant please let me know. Stefan Stefan, A couple of points: 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? BTW, it would have been more helpful to get a cygcheck output as a user for whom Cygwin doesn't work... Also, check that all the programs and the necessary DLLs are readable and executable by everyone (instead of just you). I noticed you have nontsec set, so that might be what's hiding your problem (all files look executable, but the actual ACLs don't allow other users to access them, and you don't see that via ls). On an unrelated note, it's usually not a good idea to have /cygdrive/* as a target for a mount. If I understood correctly what you're trying to do, simply connect to a network drive (using net use, for example), and assign the letter W: to it. Cygwin will automatically pick that up as /cygdrive/w. You might also want to investigate the (no)smbntsec option in the CYGWIN variable (see the User's Guide). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-'Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- 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/
Re: running the latest cygwin on a windows 2003 server
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 create the cygcheck output. The bash appears very shortly as a frame and disappears immediately again. BTW, it would have been more helpful to get a cygcheck output as a user for whom Cygwin doesn't work... Also, check that all the programs and the necessary DLLs are readable and executable by everyone (instead of just you). The initial permissions for cygwin related stuff were user: adminst group: mkgroup permissions: rwx for user and group only However, I changed these to: chmod -R o+ rX after installation '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 I noticed you have nontsec set, so that might be what's hiding your problem (all files look executable, but the actual ACLs don't allow other users to access them, and you don't see that via ls). I changed to ntsec as well - but no difference. On an unrelated note, it's usually not a good idea to have /cygdrive/* as a target for a mount. If I understood correctly what you're trying to do, simply connect to a network drive (using net use, for example), and assign the letter W: to it. Cygwin will automatically pick that up as /cygdrive/w. Ah, OK. It wasn't clear to me that cygwin automatically gathers all shared network drives. You might also want to investigate the (no)smbntsec option in the CYGWIN variable (see the User's Guide). That's interesting, too. I haven't seen this one. But no change to my problem. Stefan -- 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/
RE: running the latest cygwin on a windows 2003 server
-Original Message- From: [EMAIL PROTECTED] On Behalf Of Stefan Zachow Unfortunetly users that are not in the administrator group cannot even start a bash. That's why I took an Administrative user to create the cygcheck output. The bash appears very shortly as a frame and disappears immediately again. Tip-of-the-day: because a lot of cygwin problems manifest themselves as the shell failing to start up, and the window vanishes too quickly to see what's going on, my advice is: - start a command shell using Windoze CMD.EXE - cd root directory of your cygwin install - look at the commands in the cygwin.bat file, and enter them at the keyboard. This way, if there's any error message, you'll have time to read it. You can also use strace on the bash command to look for further clues hth, DaveK -- Can't think of a witty .sigline today -- 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/
