Re: The item "..." cannot be written, because it is locked.


Subject: Re: The item "..." cannot be written, because it is locked.
From: Bruce A. Burdick, Jr. (bucky@interaccess.com)
Date: Wed Mar 14 2001 - 02:14:29 EST


I have this same issue on 1.5pre5 on a LinuxPPC 2000 Q4 PowerMac 7300
(binary built with rpm --rebuild, then installed with rpm -i). Additionally,
copying files to the server creates an empty file despite the warning. And
deleting files results in a privileges warning -- but the files trash
anyway. And emptying the trash does not succeed. But dismounting and
remounting the volume, after such a sequence, shows the files were indeed
deleted. _But_ not for directories containing (empty) files: the files must
be trashed first (producing the false warnings) and then the empty directory
may be trashed.

The good news: I can now do encrypted logins! Can't wait until the rest
works smoothly. Keep up the good work fellas!

-B...

> From: John G Dorsey <john+@cs.cmu.edu>
> Date: Fri, 02 Mar 2001 16:06:00 -0500
> To: netatalk-admins@umich.edu
> Subject: The item "..." cannot be written, because it is locked.
> Resent-From: netatalk-admins@umich.edu
> Resent-Date: Fri, 2 Mar 2001 16:17:35 -0500 (EST)
>
> Hello,
>
> I'm running netatalk 1.5pre4 on a Linux box, with a MacOS 9.0.4 client. I've
> observed that I can create directories in volumes mounted from the Linux box
> on the MacOS client, but when I attempt to copy a file from the client to
> the mounted volume, I get:
>
> The item "<filename>" cannot be written, because it is locked.
> Do you want to continue?
>
> In perusing the archives of this list, I've come across several references
> to incorrect permissions, particularly on the .AppleDouble directory. I
> haven't had much luck in choosing various owners, groups, and modes for the
> files and directories which are being exported. (Even mode 777 doesn't seem
> to change anything.) The most recent traffic to this effect in the web
> archive appears to be from 15 Jan 2001, but I don't think there was a
> resolution posted.
>
> May I ask for suggestions as to likely culprits?
>
> Thanks!
> -jd
>



This archive was generated by hypermail 2b28 : Sun Oct 14 2001 - 03:04:34 EDT