I believe the ability to "give away" a file that you intially own is a posix-ism. Not having a copy of the spec handy to look at, I can't cite page-and-paragraph -- but it seems to me that the posix-ish behavior is to not allow non-privileged file owners to chown a file to some other user. I know that Solaris has a kernel-level toggle that is used to modify the behavior of chown in this manner.
I also seem to recall some amusing DOS attacks on deserving quota-controlled neighbors who suddenly exceeded their file system quotas without doing anything themselves.
<innocent look> of course, that was a long time ago when I was a student, and would be unforgiveably unprofessional... </innocent look>
-dan.
Little, Chris wrote:
yuck. coming from HP-UX, it allows you to "give" a file to another owner.
-----Original Message----- From: Post, Mark K [mailto:[EMAIL PROTECTED] Sent: Thursday, September 18, 2003 2:51 PM To: [EMAIL PROTECTED] Subject: Re: chown problems
You need to be root to do that. One user cannot change file ownerships to another user.
Mark Post
-----Original Message----- From: Little, Chris [mailto:[EMAIL PROTECTED] Sent: Thursday, September 18, 2003 3:48 PM To: [EMAIL PROTECTED] Subject: chown problems
I'm trying to change the ownership of a file that I as user "oracle" own to user "u55646" the following occurs
-rw-r--r-- 1 u55646 dba 583 2003-09-18 13:01 rfc1953.log -rw-rw-rw- 1 oracle oinstall 418 2003-09-18 12:55 rfc1953.sql -rw-r--r-- 1 oracle oinstall 583 2003-09-18 13:01 rfc1954.log -rw-rw-rw- 1 oracle oinstall 412 2003-09-18 12:55 rfc1954.sql -rw-r--r-- 1 oracle oinstall 5208 2003-09-18 13:01 rfc1956.log -rw-rw-rw- 1 oracle oinstall 415 2003-09-18 12:56 rfc1956.sql [EMAIL PROTECTED]:/dbatemp/rfcs/KDV1> chown u55646.dba rfc1953.sql chown: changing ownership of `rfc1953.sql': Operation not permitted [EMAIL PROTECTED]:/dbatemp/rfcs/KDV1>
