[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Executable bit set on Linux server from Windows client

From: Russ Sherk
Subject: Re: Executable bit set on Linux server from Windows client
Date: Mon, 2 Jan 2006 11:32:14 -0500

On 1/2/06, Pierre Cart-Grandjean <address@hidden> wrote:

Here are the answers:
- The file is newly created from the windows machine
- The CVSROOT is: ":pserver:address@hidden:/cvstsl/hos"
- If I manually update the executable bit on the file on the repository,
then, whatever is done on the client (checkout, update, commit ...), the
file doesn't become again executable.
- Here are the permissions (but again, please note that with any other
winows PC, as a client, we do not have the problem):
address@hidden:/cvstsl/hos/MyModule> la
total 32
drwxrwsr-x  2 cvsadmtsl      NCEDOM+ug-proj-cvs-tsl-hos-change  304
2005-12-30 14:23 .
drwxrwsr-x  9 cvsadmtsl      NCEDOM+ug-proj-cvs-tsl-hos-change  312
2005-12-30 11:13 ..
-r-xr-xr-x  1 cvsadmtsl      NCEDOM+ug-proj-cvs-tsl-hos-change  226
2005-12-30 11:53 toto.txt,v
I hope it will help you to find out what happens.

Great!  So, from your answers, it looks like it is not a  cvs issue per se.  It may be caused by the pserver-user configuration in combination with the group setuid bit on the parent directory.  I am sorry to say that I don't use pserver so I'll be of little use from here on in.

As another test, you may want to try to clear the parent dir's setuid bit (on unix side) and try to create another file from windows.

Anyone else have any ideas?



                                      Pierre Cart-Grandjean

    Russ Sherk
    <address@hidden>                                         Subject
                                      Re: Executable bit set on Linux
    02/01/2006 14:17                  server from Windows client

Hi Pierre,

On 12/30/05, Pierre Cart-Grandjean <address@hidden> wrote:

  I have a computer from wich all files commited to the linux/pserver CVS
  server have their executable bit set. This doesn't happen from any other
  computer. It doesn't depend on the login (same login on a different
  doesn't have the problem). We use CVSNT 2.0.51d.
  I didn't even think it was possible to have the executable bit set from a
  Windows client.

Could you answer these questions:
- Was the file newly created on the windows machine?
- What is the windows CVSROOT (ssh/pserver...)?
- If you manually re-set the perms (from unix), do the symptoms re-occurr
when windows checks a file in (i.e clean checkout, modify, checkin)?
- What are the permissions as returned by 'ls -l' of the
CVSROOT/module_path/parent_directory_of_the_file and the file itself?

Note: regarding windows file perms on unix - it is possible for windows to
'set permissions' on unix filesystems.  Technically speaking, it really
isn't windows doing this but the FS itself or some middleware.  For
example: a file created from windows on a shared NFS will create the file
with a dummy user (some number), group (pswin) and perms set to 777.  At
least that is how our system is set up.



  Please help. Thanks,

  Info-cvs mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]