Unsolved

This post is more than 5 years old

15 Posts

1349

April 19th, 2010 02:00

Structure of file etc/group

Anyboy have a example of this file etc/group i don't find a exemple

because i have a problem with my etc/group

this is a example of one line i have in etc/group

dicon:x:339:user1,user2,user3

with this line the last user "user3" he don't have acces

thank's for helpd

sorry for my bad english

6 Operator

 • 

8.6K Posts

April 19th, 2010 03:00

Hi Dario,

do you mean the group file on the data mover ?

if you say "no access" do you mean from an NFS client that user3 cannot access a file/dir that he should with dicon's group rights ?

Rainer

15 Posts

April 19th, 2010 04:00

is a NFS export but is accesing by a windows client

My passwd is ok

the strange is


If i add a new user "user4"
con:x:339:user1,user2,user3,user4   the "user3" have access.
and the user "user4" have no access.

is only the last user in linehe don't have acces if i put a ","it ok the last user have access

i don't know if is the normal structure of file

con:x:339:user1,user2,user3,user4,   witch this line all user have access

6 Operator

 • 

8.6K Posts

April 19th, 2010 04:00

If we are talking NFS the data mover password and group file arent relevant for determining NFS access (if you are using the default native access policy with no options to use Windows groups/ACLs for NFS access).

Like with any other NFS server and according to the protocol the NFS clients NFS request contains the numeric UID and the complete list of GID's for that user and the Celerra simply compares them to the permissions on the file.

the passwd/group files on the Celerra arent used there - its the NFS clients view of UID/GID that matters

hope that helps

Rainer

15 Posts

April 19th, 2010 04:00

yes i put the file in the datamover witch command

server_file server_2 -put group group

2 Intern

 • 

259 Posts

April 19th, 2010 07:00

What's the Access Policy set to ? Also, do you have explicit Root and R/W clients defined on the Celerra? It sounds like an ownership issue - ie: what ID is used to create the file/folder is then set as the Owner and new users (ie Windows) don't have permissions because of this.

Are the Windows users using a NFS client or coming in with Cifs share access?

If the windows clients are using a Cifs share, try setting the Access Policy on the filesystem mount to Native and export the cifs share using umask=022

Jim

6 Operator

 • 

8.6K Posts

April 19th, 2010 07:00

Is the client using NFS or CIFS ?

15 Posts

April 19th, 2010 23:00

the Filesystem is in unix mode, the windows client acces via à cifs share, but the permissions is in UNIX.

the very stange is if i add a comma "," at end of line the last user in the line have acces to folder and files.

15 Posts

April 28th, 2010 03:00

ok i find my error on file group

with command  cat -vet group

groupname:x:339:user1,user2,user3,user4,user5,^M$

The ^M shouldn't be here and that's why i have the problem.

in order to fix it :

1/ dos2unix group

2/ cat -vet group

groupname:x:339:user1,user2,user3,user4,user5,$

6 Operator

 • 

8.6K Posts

April 28th, 2010 10:00

Hi Dario,

that explains it.

you could have also seen the ^M in vi it you do a ":set list"

Rainer

No Events found!

Top