why does "chmod 666 somefile" activate ACL's ???

[Tyler Durden]

On HP-UX 11.0, doing a "chmod 666 somefile" seems to activate ACL's. WTF? In other words, an "ll -F" of the file shows that it now has a "+" at the end of the permissions.

Any ideas on how I can fix this bizarre-o behavior?

Thanks!

----cut here for example----

$ mkdir aa
$ cd aa
$ touch a
$ ll
total 0
-rw-r--r-- 1 mike users 0 Sep 27 02:11 a

(so far, everything is normal...)

$ chmod 666 a
$ ll
total 0
-rw-rw-rw-+ 1 mike users 0 Sep 27 02:11 a

(Notice that the perms now have a "+"!!!)

$ uname -a
HP-UX frog B.11.00 U 9000/800 2001143179 unlimited-user license
$ alias ll
ll=ll -F

[Stefan Farrelly · Accepted solution]

I just tried your test on some of our HP 11 servers and it DID NOT put a + (ACL) on the permissions - as is supposed to happen. This is a bug - update your patches to fix it. I cant remember which specific patch but if you use an uptodate GR patch bundle that will fix it.

[Wodisch]

Hello Tyler,

the "+" is ONLY a hint about ACLs on a file
when it is shown by the plain "ll" or "ls -l".

Is it really a "+" and not some hard to read
asterisk ('*') when using a weird font?

HTH,
Wodisch