Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!pacbell.com!tandem!netcom!dsmythe
From: dsmythe@netcom.UUCP (Dave Smythe)
Newsgroups: comp.unix.internals
Subject: Re: non-superuser chown(2)s considered harmful
Message-ID: <18687@netcom.UUCP>
Date: 13 Dec 90 07:31:30 GMT
References: <18792@rpp386.cactus.org> <1990Dec10.231812.23634@gjetor.geac.COM> <1990Dec12.052114.2694@athena.mit.edu>
Organization: Netcom- The Bay Area's Public Access Unix System {408 241-9760 guest}
Lines: 19

In article <1990Dec12.052114.2694@athena.mit.edu> jfc@athena.mit.edu (John F Carr) writes:
>In article <1990Dec10.231812.23634@gjetor.geac.COM>
>	adeboer@gjetor.geac.COM (Anthony DeBoer) writes:
>
>>Just for my $0.02 worth, if quotas are in effect, why not have a nightly
>>daemon that goes through each user's directory and blows away anything he/she
>>doesn't own?  This should take care of out-chowning files to bypass
>>allocation.
>
>It is much more polite to chown the files to the owner of the directory,

Suppose there are multiple links to the file; who gets to own it?  The last
person visited by your chown'ing utility?  Or do you only chown files with
only a single link?

D
-- 
Dave Smythe
netcom!dsmythe@apple.com   N6XLP  (also dsmythe@portia.stanford.edu)