-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Dan Armbrust on 5/4/2007 2:49 PM: > $ getfacl /bin/sh.exe > # file: /bin/sh.exe > # owner: mn04swbuild-svc > # group: Users > user::rwx > group::rwx > group:SYSTEM:rwx > group:Administrators:rwx > mask:rwx > other:rwx
Odd - no indication of restricted permissions for a non-owner. Or maybe it was just a failure of the bash postinstall script to properly update /bin/sh.exe, perhaps because you had cygwin processes still running when you originally ran setup.exe. > > Seems ok - but I tried doing the copy as you suggested - and it worked > from inside of bash - but now, low and behold, the problem has gone > away! Glad to hear it. > > Thanks! I've been fighting with this for way to long. Do you suppose > the sh.exe was just somehow corrupted? I'm not sure sh.exe was corrupted, or just the permissions to access it; but whatever it was, deleting it and starting over let correct permissions be attached to the file. And now that it's gone, we'll never know. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGO55I84KuGfSFAYARAlQwAKC4E+z9IafdWtd8iotgGw/uk4UGzwCgyzBs 3sKv8+1gy5du+1zAltCwvK4= =yxsM -----END PGP SIGNATURE----- -- 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/