1
I am using Cygwin64 2.6.0 under Windows 7.
Cygwin64 Terminal startups quickly if I don't set db_home variable in /etc/nsswitch.conf.
However if I set db_home to /%H, terminal startups very slow (30 seconds aprox.). I've googled a lot and check the Cygwin FAQ, but no luck. My HOME environment variable is correctly set, and Cygwin starts in my windows home folder.
Any idea what's happening? Thanks!
Javi Carnero
Posted 2016-10-19T13:43:43.253
Reputation: 11
1some file in the
windows home folderhas unknown ACL owner and cygwin hit a timeout asking for the relative info. It is usually better to not use the Windows Home folder as cygwin home. – matzeri – 2016-10-19T20:10:34.323@matzeri any idea on how to find the file with ACL issues? I want to set my db_home as windows home to use the .ssh folder I have in windows. Thanks. – Javi Carnero – 2016-10-20T09:47:19.203
This was a while ago, but I have run in similar issues in a large corporation with AD authentication (e.g. slow app startup, slow file search operations). The culprit is windows access control used to emulate POSIX file permissions. Cf. https://cygwin.com/cygwin-ug-net/ntsec.html for background, and https://cygwin.com/cygwin-ug-net/ov-new.html#ov-new2.4s for the responsible ACL changes. One solution is to mount the drives with the noacl option by editing the /etc/fstab file (e.g. with a line
– Peter - Reinstate Monica – 2017-05-19T09:52:37.513none / cygdrive binary,posix=0,user,noacl 0 0), but then cygwin is crippled wrt file permissions.Wrt sharing a Windows .ssh folder from cygwin: That direction should work quite well through a symbolic link from your cygwin home pointing to your Windows .ssh folder, I should think. (The other direction is less simple because Windows won't recognize simple cygwin symbolic links. With newer NTFS versions one can create native Windows links though.) – Peter - Reinstate Monica – 2017-05-19T10:04:49.587