From: Tuomo L. <dj...@ik...> - 2007-08-28 09:36:13
|
Georg Nikodym wrote: > > On Aug 27, 2007, at 11:40, Tuomo Latto wrote: > >> As to your problem, I have no idea why cygwin would see them differently. >> Do all executables have the "archive" bit set by default? > > I'm very curious what the significance of the archive bit is expected to > be. Well, maybe I should have explained a bit further that this was a question meant for everybody. No actual expectations here. Sorry to mislead you. I've never really used cygwin, so I have no idea how the permissions work there. I was sort of wondering out loud if that might play a part, file attributes as they are. > I've chased this issue down further and the plot thickens a bit. > > My test program may or may not work as expected depending the directory > in which it's run. Further digging shows that if cygwin creates the > directory, my test works. If cmd.exe or some other program create the > directory, then the test fails. > > I've been fooling around with cygwin getfacl/setfacl since that's where > the difference appears to be... I wonder if this helps: http://www.cygwin.com/cygwin-ug-net/ntsec.html > It's looking definitely like this is not really a mingw problem at all. Well, yes. If the executable works in plain Windows, the fault must lie within Cygwin. -- Tuomo ... Please reply if you don't get this message |