Subject: Re: Can't Empty Trash
From: Marc Miller (itlm019@mailbox.ucdavis.edu)
Date: Fri Nov 17 2000 - 16:53:05 EST
The dropkludge fix simply changes the behavior of afpd so that files
written to a directory inherit its uid/gid owners and write permission
settings. It solves the problem I had before with files getting dropped
into dropboxes that the owner of the dropbox can't read.
But I'm not quite sure whether deleting a file acts as a
copy/move to the Network Trash folder or whether it's an entirely
different procedure altogether.
Do a "ls -al" on your Network Trash folder. If the owners/write
permissions are different than those of ".", let me know and I'll
spend next week fixing it. If dropkludge is working properly, the files
may have read permissions that the directory doesn't. afpd and/or MacOS
assumes that it can read files even when the user logged in can't.
On Fri, 17 Nov 2000, Michal 'CeFeK' Nazarewicz wrote:
> On Thu, 16 Nov 2000, Marc J. Miller wrote:
>
> > I can think of some permission schemes on the Network Trash Folder that
> > might cause problems if you have dropkludge enabled. Is anyone using that?
>
> I am using dropkludge fix... what's this? I've enabled this, hoping that
> this will solve my (dealt with) problems.
>
> --
> Michal 'CeFeK' Nazarewicz
> Linux Registered User 164007
>
>
============================================================
/\/\arc ._|. /\/\iller (itlm019@mailbox.ucdavis.edu)
Computer Room Consultant
Information Technology/Lab Management
============================================================
I can be contacted through the Communication Center link from
http://www.mother.com/~mjmiller/
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:32:39 EST