ClearCase MVFS文件权限 [英] ClearCase MVFS files permissions

问题描述

我开始了解在Git和ClearCase之间的存储库同步期间遇到的问题.

I am starting to understand the issues I get during my repository synchronization between Git and ClearCase.

让我们看看这个:

$ cd
$ touch foo && chmod 777 foo
$ ls -al foo
-rwxrwxrwx+ 1 ch52198 Domain Users 0 Sep  4 15:04 foo
$ cd /vob/view/project/
$ cp ~/foo .
$ ls -al foo
$ -rw-r----- 1 ch52198 Domain Users 0 Sep  4 15:05 foo
$ chmod u+x foo
$ ls -al foo
$ -rw-r----- 1 ch52198 Domain Users 0 Sep  4 15:05 foo

ClearCase做错了所有事情.使用MVFS存储时，它将忽略所有文件权限.

ClearCase is doing everything wrong. It ignore all the files permissions when using a MVFS storage.

事情变得越来越糟，因为如果在我的本地Git存储库中，我在脚本上设置了可执行标志.我将永远无法在我的ClearCase存储库中保留此标志.

Things are getting worse because if on my local Git repository I set the executable flag on a script. I will never be able to keep this flag on my ClearCase repository.

我应该如何解决此问题?

How should I fix this issue?

我尝试使用 cleartolprotect -chmod 777 foo ，但是我看不到Cygwin的权限更改.

I tried to use cleartol protect -chmod 777 foo, but I cannot see the permission change with Cygwin.

推荐答案

对于已复制的文件，您需要一个

For the files you have copied, you would need a cleartool protect -chmod to restore the permission.

还要检查视图中的 umask .这将确定在ClearCase视图中如何设置与文件关联的mod.

Check also the umask you have in your view. That will determine how the mod associated to the file is set in a ClearCase view.

另请参见"动态视图中视图专用文件的访问控制"

在Linux和UNIX系统上，视图私有文件的初始所有者，组和保护模式由以下规则确定:

On Linux and the UNIX system, the initial owner, group, and protection mode for a view-private file are determined by the following rules:

• 所有者.最初的所有者是创建文件或目录的过程的用户.
• 组.初始组是创建文件或目录的过程的主要组.
• 保护模式.视图专用文件的初始保护模式取决于创建文件或目录的用户的umask.umask是Linux和UNIX系统上支持的设置，它指定用户创建文件时不授予某些权限.(有关详细信息，请参见Linux或UNIX系统上的umask参考页面.)
  当用户创建视图专用文件或目录时，Rational ClearCase将从一组权限开始，这些权限取决于文件或目录的创建方式.然后，用户的umask指定的权限将由Rational ClearCase删除.
  例如，如果用户的umask为002，则Rational ClearCase会删除其他用户的写许可权.

• Owner. The initial owner is the user of the process that creates the file or directory.
• Group. The initial group is the primary group of the process that creates the file or directory.
• Protection mode. The initial protection mode for a view-private file depends on the umask of the user who creates the file or directory. A umask is a setting supported on Linux and the UNIX system that specifies that some permissions are not granted when the user creates a file. (For details, see the umask reference page on Linux or the UNIX system.)
  When a user creates a view-private file or directory, Rational ClearCase begins with a set of permissions that depend on how the file or directory is created. The permissions specified by the user’s umask are then removed by Rational ClearCase.
  For example, if the user’s umask is 002, write permission for others is removed by Rational ClearCase.

这篇关于ClearCase MVFS文件权限的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！