Clearcase-无法访问VOB-ls:读取目录-权限被拒绝 [英] Clearcase - Unable to access VOB - ls: reading directory - Permission denied

问题描述

Clearcase Server Version - 8.0.1.19
OS – Centos - 7.6.1810 (Core)

问题::创建了新的VOB，安装了VOB，然后在服务器上成功创建了动态视图.从VOB根目录ls命令显示以下错误.

Problem: Created new VOB, Mounted the VOB then created dynamic view on server successfully. From VOB root directory ls command shows below error.

ls: reading directory .: Permission denied
total 0

我已经在下面执行了保护命令.

I have executed below protect commands.

cleartool protectvob -f -chown ccadmin -chgrp testvob-grp /vobstg/testvob.vbs
cleartool protect -chown ccadmin -chgrp testvob-grp -chmod 775 -r .


[root@VOB-Server /]# cleartool desc -l vob:/vobstg/testvob
versioned object base "/vobstg/testvob"
  created 2019-11-21T09:01:57+05:30 by ccadmin.testvob-grp@VOB-Server
  "This is test VOB."
  protected by rolemap: "DefaultRolemap"
  effective access for user "root": rmelem,Read
  VOB family feature level: 8
  VOB storage host:pathname "VOB-Server:/vobstg/testvob.vbs"
  VOB storage global pathname "/net/VOB-Server/vobstg/testvob.vbs"
  database schema version: 80
  modification by remote privileged user: allowed
  atomic checkin: disabled
  srfm: disabled
  evil twin detection: disabled
  VOB ownership:
    owner ccadmin
    group testvob-grp
  minimum client feature level: 8
  ACLs feature level: 8
  Attributes:
    FeatureLevel = 8

视图所有者具有rwx(全部)权限.因此，在较新版本的Clearcase中，我是否需要为根ID和VOB所有者ID启用配置?

View owner has rwx (all) permission. So in newer version of Clearcase do I need to enable configuration for even root id and VOB-owner ID?

我正在使用默认配置规范

I am using default config spec

element * CHECKEDOUT
element * /main/LATEST

使用根帐户创建的动态视图.描述VOB标记时，它显示以下错误.

Dynamic view created with root account. While describing the VOB tag it shows below error.

[root@VOB-Server]# cleartool desc -l /vobstg/testvob
cleartool: Error: No permission to resolve: "/vobstg/testvob".
cleartool: Error: Unable to access "/vobstg/testvob" because either it is unreadable or its containing VOB is not accessible to the current user.

使用VOB所有者的帐户/ID( ccadmin )，我可以描述VOB.

Whereas with VOB Owner’s account/ID (ccadmin), I can able to describe the VOB.

推荐答案

首先，这取决于您的配置规范(我假设 element */main/LATEST )

First, it depends on your config spec (I will assume element * /main/LATEST)

第二，您的问题提到 root @ VOB-Server :确保以视图所有者的身份进行 ls 测试: ccadmin.testvob-grp

Second, your question mentions root@VOB-Server: make sure to do the ls test as the view owner: ccadmin.testvob-grp

仍然是视图所有者，请执行 id -a 检查主要组(或其中一个辅助组)是否属于VOB组(VOB，不是视图)的一部分，这是正确的受保护的)

Still as the view owner, do a id -a to check if the primary group (or one of the secondary groups) is part of the VOB group (VOB, not view, which is correctly protected)

请参见" VOB的访问控制和" 关于VOB的组列表中的其他组"

您可以使用 cleartool describe 命令显示VOB的所有者，组和补充组列表.

You can use the cleartool describe command to display the owner, group, and supplemental group list for a VOB.

cleartool descr -l vob:/vobs/vobtag

使用VOB所有者的帐户/ID(ccadmin)，我可以描述VOB.

Whereas with VOB Owner’s account/ID (ccadmin), I can able to describe the VOB.

这是预料之中的:只有将主要Vob组作为其组的一部分的用户才能访问Vob. root 在其组中没有 testvob-grp ( id -a )

That is expected: only user with the primary Vob group as part of their group would be able to access the Vob. root has not testvob-grp in its groups (id -a)

这篇关于Clearcase-无法访问VOB-ls:读取目录-权限被拒绝的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！