Is your CYGWIN environment variable set to "ntsec"? In my experience with Clearcase and cygwin, cygwin can do permissions on NTFS, but has weird errors on things like MVFS and Samba shares. I would not be surprised if TAS ran into similar weird permissions problems when using cygwin. Have you tried creating the file with another command, like:
echo "" > file.txt Does that result in the same permissions? Have you tried touching the file and then chmod-ing it? Have you tried creating a view stored on the windows box- does it have the same results? HTH, Peter Sharona Rozmaryn wrote: > Hi. > > We have a group of developers using cygwin with Windows, as well as > ClearCase. The ClearCase data (VOBs and Views) are stored on UNIX > servers. In order to access the UNIX servers, we use TAS 6.1, which > allows transparent access between > the UNIX server and the PC clients. > > This group of developers is trying to build software from Windows. > Their build script has a "touch" command which > works OK outside of ClearCase, but with ClearCase, it somehow does not > recognize the umask of 002 so it makes the permissions read only. The > file that is touched get created, but there is a permission error that > causes the build to fail. > > Do you have any ideas about how to fix this problem? > Thanks for any help. > > -- Sharona Rozmaryn > > Hughes Network Systems > Tel: (301) 601-4059 > Fax:(301) 601-4091 > Email: [EMAIL PROTECTED] > > > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Bug reporting: http://cygwin.com/bugs.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
