Post #2421358

2026-04-28 19:40 UTC

@theirongiant@hachyderm.io @nikdoof@social.doofnet.uk @dmark@hachyderm.io IIRC the default file path was changed a while back, but I think you can customize it at compile time. I took a gander at the docs, and on https://netatalk.io/docs/Getting-Started it says to run “afpd -V" which will print the path to the configuration file that it is using. EDIT: and on https://netatalk.io/docs/Troubleshooting the first question/answer actually says to confirm that the afp.conf file you edited is in the correct location. So you're not the only person who's run into this problem!

Replies (3)

@theirongiant@hachyderm.io 2026-04-28 21:25

@smallsco@oldbytes.space @nikdoof@social.doofnet.uk @dmark@hachyderm.io OK, I see the problem. I was only reading the section marked "Documentation." You're showing me something in the section labeled "Wiki." Why do both (need to) exist? Wiki often serves as documentation, and documentation contains some elements from the wiki.

Open ##2421359
@theirongiant@hachyderm.io 2026-04-28 21:42

@smallsco@oldbytes.space @nikdoof@social.doofnet.uk @dmark@hachyderm.io Also... I did run "afpd -v" and that's how I figured out my next issue: that MySQL hadn't been configured yet. I took care of that, fixed the permissions, and ran afppasswd to set the AFP password for my own account. Now I have in a working state a configuration that I would consider typical for #GlobalTalk : when logging in as Guest, I see one share with RW access (the free-for-all folder), and one folder with read-only access (sharing content for GT visitors). When I login with a known account, I see the guest shares AND my "home" folder (which is actually /home/piadmin/afp-data).

Open ##2421360
@dmark@hachyderm.io 2026-04-29 18:10

@smallsco@oldbytes.space @theirongiant@hachyderm.io @nikdoof@social.doofnet.uk indeed, editing the wrong config file is a recurring pitfall (that I myself have fallen into more often than I like to admit) which is why I made sure there was a section on this in the Troubleshooting guide the #netatalk build system does default to /usr/local/etc for config files, because this is the FHS compliant location for user installed software, and this has been the case since at least netatalk v3.2.0 (when we moved to meson) a downstream packager can then customize this location to comply with the filesystem scheme of their particular OS distribution, which Debian does for example with /etc/netatalk this is why you typically get totally different software installation paths with a binary package vs. building from source code, which can be obnoxious but an unavoidable quirk of Unix-like operating systems that you have to get used to if you take a look at the Netatalk Compilation guide: https://netatalk.io/compilation the Debian build example includes "-Dwith-pkgconfdir-path=/etc/netatalk" so that you get the customary config file path on that particular OS HTH!

Open ##2421361