Subject: RE: and yet muddier
From: Chris Herrmann (chris@faredge.com.au)
Date: Tue Jul 10 2001 - 18:55:33 EDT
No, it's not related to Linux permissions on the Network Trash folder -
first thing I checked. They're all logging in as guest users atm, which
would obviate any user/group permission issues - it behave exactly the same
way as when it was running with user perms.
The way to get around user/group problems for folders is to setgid the
directory (g+s <directory>).
It's definitely related to locking, because if a user doesn't use the
network trash for a long time (where a long time is an unspecified number of
minutes/hours/???) then another user can automagically start using it (found
this out last night by accident).
Recompiled with --enable-dropkludge last night - am already
trying --with-lastdid. Using --with-lastdid has meant that I don't see
millions of messages about conflicting DIDs, so it must be doing something
right!
Will let you know how it goes today... fingers crossed.
-----Original Message-----
From: Bryn Hughes [mailto:bhughes@vcc.bc.ca]
Sent: Wednesday, 11 July 2001 00:45
To: netatalk-admins@umich.edu
Subject: Re: and yet muddier
Actually, this is because the client creates the Network Trash folder if it
doesn't exist. Since it's created by the client, the first client to
connect creates it and it is only writeable by them.
If you change the permissions on the Linux side to allow all users to write
to the Network Trash folder and its subfolders, the problem will go away.
Bryn
This archive was generated by hypermail 2b28 : Sun Oct 14 2001 - 03:04:44 EDT