

Hopefully you don't have so many users who need to modify the web root that this will become cumbersome.

What I'd do is share out the web root directly over SMB, make a bunch of Samba users, and make sure your permissions ducks stay in a row.

Personally I'd think in this case Samba would be fine. The question then becomes which of the latter will serve your needs the best. If you don't want to upset the system you have right now with symlinking, I'd drop AFP in favor of SMB or NFS (actually I'd drop AFP in any event but whatever :p). You have been warned.Other results of googling seem to confirm your experience that ".it shows up as an application." If you still insist on using them, be aware you're heavily violating the specs. There's currently no way this can be resolved, as we either end up with two file/dirs having the same id, or a file having two parents. With a symlink a file/directory "exists" twice, something AFP doesn't allow. From a bit of googling ("afp symlinks") it sounds like, well, here it is straight from netatalk's documentation ():ĭon't use unix symlinks. but this sounds like a limitation of AFP itself.
#NETATALK DISCONNECT USER MAC#
Reading the AFP docs and Avahi docs might shed some light.ĭon't count me as a Mac geek. I was kind of lost as to where to start sleuthing. Is this maybe some kind of lease running out? Or a default timeout that I could increase/eliminate?Īgain, thanks for all the help - while I'd love to have more actual answers at least this gives me some directions to try. I have to restart Avahi in order for it to show up again. This might be a separate issue but I'm noticing that the Linux server in Finder ends up timing out a lot and being disconnected. I guess I'm in need of a Mac user who's nerdy enough to know the ins and outs of AFP and still loves Linux. I think the question of AFP not following symlinks is a big one.does anyone out there know AFP? I can make aliases in the Finder if I go to the server (in the Finder) and then move them around.Īvahi and Netatalk are what's been serving the directories to AFP. So unless we can all share each others' $HOME/public_html dirs, it'll be better to have it all in one place. For instance, one person might be doing index.php work one day, and then the next, someone else will be fixing a different issue. Of these, the one I like best is the $HOME/public_html directory but the problem is that we all work on the same project at the same time.
