strange file permission

[Luc Monnens]

Hi all,

I have a file with -rw-------+ file permission.
I can change the ugo rights with chmod, but I cannot get rid of the +

1. How do I change the rights before and after ugo?

2. What is the meaning of this +?

I have an Itanium running hp-ux 11iv2.

Any input will be appreciated.

Thank you.

Luc Monnens

[Muthukumar_5]

I hope it is related nis+ related files?? Where did you find that file.

1. How do I change the rights before and after ugo?

Using chmod only.

chmod file. See chmod man page.


--
Muthu

[Steven E. Protter]

Shalom Luc,

A bit odd.

chmod 0000 filename

does that help?

Don't forget to make the permissions normal when complete.

What is the name of the file, that might be helpful in tracking this down. Full path please.

SEP

[Hemmetter]

Hi Luc

This + may indicate that there are an Access Control List ACl on that file.

man ls(1) section ACL, and lsacl(1)

rgds
HGH

[Luc Monnens]

Some more info.
I am running CIFS 02.01.02 (Samba 03.07) and the file in question is an Excel spreadsheet.

Luc

[Raj D.]

Luc,

If ACL is on that file , you can check with lsacl and file name.

for details : $ man lsacl // $ man acl

hth,
Raj.

[Muthukumar_5]

Is that file only having that permission? Can you create a new file and check the permission.

We may not change the right before ugo.. since it is based on file type.

--
Muthu

[Luc Monnens]

"#chmod 0000 test.xls" makes the rights
----------+

"#lsacl -l test.xls" gives
"#lsacl: file "test.xls": Function is not available (errno = 251)"

"#touch test" creates a file with -rw-rw-r-- permissions.

[john korterman]

Hi,

check Document ID: KBRC00001987 in the tech base.

regards,
John K.

[Vipulinux]

hi

try giving
chmod 1000

does this helps

cheers

[Luc Monnens]

chmod 10000 makes it ---------T+

Document ID: KBRC00001987 is about getting a "+" when doing an ls -al.
So that is indeed what happens.
It points to no ACLs being attached.
ANd the "+" only shows when doing the first ls -al after NFS mounting a directory.
This apparently happens when certain patch dependecies are missing.
So far this document.

The directory with this file is not nfs mounted.

My system was installed last week from the December 2005 release. So it should be pretty up to date.

I did a patch analysis, but how do I determine which patch I should apply to make sure this "+" does not show up anymore?

But most importantly what does this "+" means AND how do I get rid of t?

Luc

[Luc Monnens]

Hi all,

I do appriciate the input I got, but none of the replies really helped - hence the low points.

Is there anybody else out there who has seen and dealt with this before?

Kind regards,

Luc

[Elmar P. Kolkman]

Luc,

According to the manual page of ls on 11iv1, if you are using JFS you should use getacl instead of lsacl to look at ACL contents. And the + should only be displayed for files having ACL's (which isn't strange for CIFS-exported filesystems).
Perhaps you missed something in your ls manual page on 11iv2 (I don't have one to look at this right now).

Hope this is of more help to you.

Kind regards,

Elmar

[Steven E. Protter]

Luc,

It is possible the file has an ACL associated with it.

If possible, copy the file elsewhere, remove it and then copy it back.

SEP

[Luc Monnens]

Hi,

Yes lsacl is not working, but getacl is.

Why would it make sense to have ACLs when using CIFS?
Can you point me to anywhere I could find more info on CIFS and ACLs?

Copying the file elsewhere, copies the + with it.

-------------------------------------------

Some more info: We have these files on our CIFS and users access them fine from their Office applications, modify them and save them. The next time they open them they get a "read only" notifycation.
When we check on the hp-ux file level we see that the rights have changed from -rwxrwx--- (for instance) to -r--rwx---+.
We can chmod them back to -rwxrwx---+ and the user can write to the files again.

--------------------------------------------

Would this be caused by ACL settings somewhere?
Where should I start looking?

Kind regards,

Luc

[john korterman]

Hi,

take a look at Document ID: KBRC00003073
in the tech base.

regards,
John K.

[Elmar P. Kolkman]

CIFS has a different security policy as unix. In unix we accept that a file is assigned to a single group and user, while the CIFS model can assign multiple groups to a file... To do this on unix, you need to use ACL's.

But your problem indicates the ACL's aren't working as expected: they are correctly created, but the resulting mode of the file is incorrect.

The user in question, can you look into which groups he is part of? And if any of those match the groups in the ACL?
And I think you might check your CIFS configuration. Perhaps there is a problem with the umask, being set to 200 instead of 002, meaning the write bit of the user is always turned off when creating a file...

I don't have a lot of experience with CIFS and ACL's, so anyone with more experience, please correct me if I'm wrong. ;-)

[Luc Monnens]

I am still looking into this - and more in particular to actually use ACLs - but wanted to close this thread.