This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: can't chmod files that I own


I had the exact same problem with Cygwin & CVS.  

I think the problem is that NT's idea of "perry" doesn't match Cygwin's
definition of UID 1119.  If you're on an NT Domain, have you done the
"mkpasswd -u perry -d COMPANY_DOMAIN >> /etc/passwd"?  That's what fixed it
for me.

See this for another workaround:

	http://cygwin.com/ml/cygwin/2002-09/msg01167.html


-----Original Message-----
From: Jeff Perry [mailto:jsp@mail.utexas.edu]
Sent: Wednesday, September 25, 2002 5:19 PM
To: cygwin@cygwin.com
Subject: can't chmod files that I own


I have read the documentation on 'ntsec', but I still don't understand why I
can't chmod files that I own.  I noticed this when using cvs.

For example:

$cvs update
cvs server: Updating .
U blah.cpp
cvs update: cannot change mode of ./blah.cpp: Invalid argument
$ ls -l
total 54
drwxrwxrwx    2 Administ None         4096 Sep 25 14:47 CVS
-rw-rw-rw-    1 1119     None          871 Sep 25 14:15 blah.cpp

Here is another example that doesn't involve cvs:

$ whoami
perry
$ echo text > temp
$ ls -l
total 1
-rwxrwxrwx    1 1119     None            5 Sep 25 14:56 temp
$ chown Administrator temp
$ chmod -x temp
$ ls -l
total 1
-rw-rw-rw-    1 Administ None            5 Sep 25 14:56 temp

perry cannot chmod a file owned by perry, but perry can change the file's
ownership to Administrator and then chmod the file.


--
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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]