可能是因为该组缺乏对父目录的（读取和）执行权限。
例如，
mkdir /tmp/secret chmod 600 /tmp/secret touch /tmp/secret/publicfile chmod 644 /tmp/secret/publicfile
组成员将无法访问 /tmp/secret/publicfile。
还有可能产生干扰的 POSIX ACL 和/或 xattrs（扩展属性）。除此之外，我只想到 AppArmor、SELinux 策略。
哦，组成员身份在下次登录时将变为活动状态（因此，如果用户最近添加到特定组，他们可能只需要重新登录）
probably because the group lacks (read and) execute permissions on the parent directory/directories.
E.g.
/tmp/secret/publicfile will not be accessible to group members.
There are also POSIX ACLs and or xattrs (extended attributes) that might be interfering. Besides that only AppArmor, SELinux policies come to mind.
Oh and group membership becomes active on the next login (so if users were recently added to the particular group, they might just need to relogin)
也许你指的是特权而不是面具。644表示该用户可以写入和执行，但不能读取或复制。您可以尝试 655，这意味着：其他用户可以读取并执行我的文件。
Perhaps you mean the privileges not the mask.644 means that this user can write and execute, but cannot read nor copy. You could try 655 which means: other users can read and execute my file.
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
暂无简介
文章 0 评论 0
接受
发布评论
评论（2）
可能是因为该组缺乏对父目录的（读取和）执行权限。
例如，
组成员将无法访问 /tmp/secret/publicfile。
还有可能产生干扰的 POSIX ACL 和/或 xattrs（扩展属性）。除此之外，我只想到 AppArmor、SELinux 策略。
哦，组成员身份在下次登录时将变为活动状态（因此，如果用户最近添加到特定组，他们可能只需要重新登录）
probably because the group lacks (read and) execute permissions on the parent directory/directories.
E.g.
/tmp/secret/publicfile will not be accessible to group members.
There are also POSIX ACLs and or xattrs (extended attributes) that might be interfering. Besides that only AppArmor, SELinux policies come to mind.
Oh and group membership becomes active on the next login (so if users were recently added to the particular group, they might just need to relogin)
也许你指的是特权而不是面具。
644表示该用户可以写入和执行，但不能读取或复制。您可以尝试 655，这意味着：其他用户可以读取并执行我的文件。
Perhaps you mean the privileges not the mask.
644 means that this user can write and execute, but cannot read nor copy. You could try 655 which means: other users can read and execute my file.