Daniel E. Lautenschleger | 1 Oct 2001 20:07
Picon

Odd Log Messages

afp_getforkparams: of_find: No such file or directory

afp_enumerate: stat Zip 100: No such file or directory

Can someone tell me what these syslog messages indicate?

Thanks.
-Dan

Joe Clarke | 1 Oct 2001 21:09
Favicon

Re: Odd Log Messages


On Mon, 1 Oct 2001, Daniel E. Lautenschleger wrote:

> afp_getforkparams: of_find: No such file or directory

This error gets returned if of_find() fails to locate an open fork in the
ofork hash table.

>
> afp_enumerate: stat Zip 100: No such file or directory

This error is returned if stat fails in the afp_enumerate() function.

What might be happening here is that a file or directory was deleted
outside of afpd, and afpd is trying to cope with the change the best way
it knows how.

Joe

>
>
> Can someone tell me what these syslog messages indicate?
>
> Thanks.
> -Dan
>
>
> _______________________________________________
> Netatalk-devel mailing list
> Netatalk-devel <at> lists.sourceforge.net
(Continue reading)

Daniel E. Lautenschleger | 1 Oct 2001 22:08
Picon

Netatalk Permissions

I've been curious about Netatalk permissions for some time now as I really
don't understand what the proper setup is. The only thing I do know is
that if you want new files and directories under a shared volume to be
created with the same group as the volume, you need to SGID the volume
perms for the group. I wish Netatalk would just look at the parent
directory where data is being created and mirror the permissions.

So, how should permissions be set up on a shared Netatalk volume? What
perms should be applied to the data in a directory? How about the .AppleD*
directories in that directory as well as the Network Trash Folder,
TheFindByContentFolder, and TheVolumeSettingsFolder?

I've also noticed the sticky bit being set on certain occasions. When
would the sticky bit apply?

Thanks.
-Dan

Joe Clarke | 1 Oct 2001 22:18
Favicon

Re: Netatalk Permissions


On Mon, 1 Oct 2001, Daniel E. Lautenschleger wrote:

> I've been curious about Netatalk permissions for some time now as I really
> don't understand what the proper setup is. The only thing I do know is
> that if you want new files and directories under a shared volume to be
> created with the same group as the volume, you need to SGID the volume
> perms for the group. I wish Netatalk would just look at the parent
> directory where data is being created and mirror the permissions.

FreeBSD has a cool kernel option that allows certain volumes to be mounted
in such a way that this kind of thing is done.  The docs say you should
only turn on SUIDDIR o dedicated Samba/netatalk filesystems.

On other filesystems, I just set the setgid bit on the the main directory,
and everything seems to fall in line just fine.  Various file ownerships
will happen from time to time, but the group stays the same (as does rwx
perms), so files are still deletable and changeable.

>
> So, how should permissions be set up on a shared Netatalk volume? What
> perms should be applied to the data in a directory? How about the .AppleD*
> directories in that directory as well as the Network Trash Folder,
> TheFindByContentFolder, and TheVolumeSettingsFolder?

I usally grant a certain group access to a given share, and do a chmod
2770 <dir name>.  From there on out, things work quite well.

>
> I've also noticed the sticky bit being set on certain occasions. When
(Continue reading)

Andy Wettstein | 1 Oct 2001 23:17
Favicon

netatalk and trustees

Hi

I've been trying to get trustees and netatalk to work together, but
netatalk doesn't honor the trustee configuration.  Is there something
special about how netatalk gets its file permissions?

Of course if any has any other information about any other ways to get
ACL's working correctly, I'd be glad to hear it.  Does any of the other
ACL stuff work correctly with netatalk?

thanks

andy

Joe Clarke | 1 Oct 2001 23:28
Favicon

Re: netatalk and trustees


On Mon, 1 Oct 2001, Andy Wettstein wrote:

> Hi
>
> I've been trying to get trustees and netatalk to work together, but
> netatalk doesn't honor the trustee configuration.  Is there something
> special about how netatalk gets its file permissions?
>
> Of course if any has any other information about any other ways to get
> ACL's working correctly, I'd be glad to hear it.  Does any of the other
> ACL stuff work correctly with netatalk?

I've never used netatalk with ACLs, but everywhere I've seen, netatalk
uses stat to get the mode on files and directories.

Joe

>
> thanks
>
> andy
>
>
> _______________________________________________
> Netatalk-devel mailing list
> Netatalk-devel <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/netatalk-devel
>
>
(Continue reading)

Daniel E. Lautenschleger | 2 Oct 2001 03:22
Picon

PC MacLan

Anyone using PC MacLan on a PC for accessing Netatalk volumes?

Is there a way to block people from using PC MacLan on a Netatalk volume?
I'd rather have PC users use Samba.

Thanks.
-Dan

Karen A Swanberg | 2 Oct 2001 23:01
Picon

cnid/did/flocks/what? - wishlist

I'm going to do the evil, and ask for a bit more documentation. I too am
starting to get files deleted from my netatalk directories, and while I've
gone through the archives to try to figure out which compile flag I should
be setting to help with this, I'm getting hopelessly confused. Is it
--did, -flock-locks or what?

So, here's what would be nice: a document that explains the ./configure
flags in a sentence or two, including what problems it's supposed to fix,
and what OSes they apply to, at least in general terms (bsd vs linux or
something like that, i.e. isn't one of those new flags specific to OSX
support?).

I pulled down the netatalk-admins archive last night, and tried to start
compiling such a documentation list, but as I don't understand what half
of the flags are doing or what they're meant to fix, I didn't get very
far...

For me specifically, the flags that confuse me, and which I think I might
need, are:

--enable-cnid-db, --with-did=[scheme] (and what scheme does what?),
--with-flock-locks.

Posting it to netatalk-admins would be nice, too, as then it would go into
the archive... and of course, if these were set to print out in
./configure --help, that would be great, too, but I realize space is
limited.

(ah, a bit of an update, checked the user forums on sourceforge, and found
a post by Joe saying that --with-flock-locks and --enable-did=last should
(Continue reading)

Joe Clarke | 3 Oct 2001 00:53
Favicon

Re: cnid/did/flocks/what? - wishlist

I'd be happy to help with documentation.  I just got back from a big
netatalk site, and things seem to be going okay.  I rolled out
--with-flock-locks (on FreeBSD 4.4-STABLE), and they say the Quark problem
improved....I'll let that sit for a while, and see if they still think
things are better.

There are still bugs in afpd.  I still notice core dumps related to the
ofork code that I'm trying to track down.  However, the way it works now
is at least usable.

Joe

On Tue, 2 Oct 2001, Karen A Swanberg wrote:

>
> I'm going to do the evil, and ask for a bit more documentation. I too am
> starting to get files deleted from my netatalk directories, and while I've
> gone through the archives to try to figure out which compile flag I should
> be setting to help with this, I'm getting hopelessly confused. Is it
> --did, -flock-locks or what?
>
> So, here's what would be nice: a document that explains the ./configure
> flags in a sentence or two, including what problems it's supposed to fix,
> and what OSes they apply to, at least in general terms (bsd vs linux or
> something like that, i.e. isn't one of those new flags specific to OSX
> support?).
>
> I pulled down the netatalk-admins archive last night, and tried to start
> compiling such a documentation list, but as I don't understand what half
> of the flags are doing or what they're meant to fix, I didn't get very
(Continue reading)

Alistair Riddell | 3 Oct 2001 01:12
Picon
Favicon

Re: cnid/did/flocks/what? - wishlist

On Tue, 2 Oct 2001, Joe Clarke wrote:

> There are still bugs in afpd.  I still notice core dumps related to the
> ofork code that I'm trying to track down.  However, the way it works now
> is at least usable.

It certainly is very usable - I run a network of 600 machines from
netatalk servers. Most of those machines netboot from a netatalk server.

Biggest problems I have are cnid-db not yet working properly, and
case-sensitivity issues (I don't want to casefold:tolower all my users'
files....)

--

-- 
Alistair Riddell - BOFH
IT Manager, George Watson's College, Edinburgh
Tel: +44 131 447 7931 Ext 176       Fax: +44 131 452 8594
Microsoft - because god hates us


Gmane