Detect if Solaris has chown restricted

chownsolaris

I am trying to chown a file, and I am getting a Not ownermessage

bash-3.00$ uname -a
SunOS host001 5.10 Generic_138888-03 sun4u sparc SUNW,SPARC-Enterprise
bash-3.00$ id
uid=60010(user1) gid=910(web)
bash-3.00$ ls -l file.ext
-rwxrwxrwx   1 user1  web        17449 Feb 14 10:53 file.ext
bash-3.00$ chown user2 file.ext
chown: file.ext: Not owner

How could I detect if this machine has restricted chown usage?

Best Answer

getconf _POSIX_CHOWN_RESTRICTED / checks the setting on the / directory, POSIX allows different paths to have different values, such as local filesystems vs. NFS, hence the requirement to include a path to the directory or file you want to know about.

Related Solutions

Chown root mistake

Did you tell it to recursively apply it?

You may find that it did not apply it recursively in which case only the top level will be userx:uxery so you don't actually have to change anything except root:root again.

If you DID NOT chown -R then it should still be fine.

How to Chown a directory recursively including hidden files or directories

I'm pretty sure the -R flag does work - it always has for me anyway. What won't work, and what tripped me up early in my command line usage, is using * in a directory with hidden files/directories. So doing

$ chown -R /home/user/*

will not do the hidden files and directories. However if you follow it with

$ chown -R /home/user/.[^.]*

then you will do all the hidden files, (but not . or .. as /home/user/.* would do). Having said all that, I would expect

$ chown -R /home/user

to get all the hidden files and directories inside /home/user - though that will of course also change the permissions of the directory itself, which might not be what you intended.

Best Answer

Related Solutions

Chown root mistake

How to Chown a directory recursively including hidden files or directories

Related Topic