Subject: so, options:noadouble just plain doesn't work?
From: Charles Mangin (charles@burneydesign.com)
Date: Thu Sep 27 2001 - 14:53:45 EDT
after banging my head on the problem i described in a previous email
- namely that i could copy files to my netatalk linux server without
trouble except when said files were enclosed in a folder - i watched
closely on the server what exactly was going on. i mistakenly thought
that there was one .AppleDouble directory at the root of a
mountpoint, like there is one .AppleDesktop, and that that was having
permission problems. chowning and chmodding it made no difference.
then i realized there was a .AppleDouble inside every folder i
created, despite the fact that i had specified noadouble in the
options in the server config file. realizing that was what was having
permission problems, i turned off that switch, and the problem went
away.
so, essentially, with noadouble enabled, the idea is not to create a
.AppleDouble until it's absolutely necessary - i.e. when there is a
file that has a resource fork copied onto the server - but the
directory is created anyway, even though there might not be anything
in it. when something does have to go in there, the permissions
aren't set right, so the resource fork can't be written there, and it
fails, giving up with a -50 or "file is locked" error on the client.
with noadouble disabled, the .AppleDouble is created as always, but
with the correct write permissions, since it knows ahead of time that
resource forks are going to be written willy-nilly.
this, of course, is only how i understand it. i'm probably wrong or
terribly misguided. please clarify anything that i've missed.
This archive was generated by hypermail 2b28 : Sun Oct 14 2001 - 03:04:53 EDT