DaveSchmenk wrote:
To add even more gas to the fire... I updated my Debian box yesterday and it pulled in version 2.0.5-3 of netatalk. No problem, I just rebuild from source, same as always. Except this time, no dice. Confusion abounds. Finally I am able to see my server from the IIGS, but I can't login in. Wrong password. I use a ~/.passwd file and I know it is the correct file. I review the syslog file and it has lots of stuff listed about cinb and cdb errors. There is a line about an incompatible .AppleDB file. I don't have a clue what that is, but I figure I'll delete it and let netatalk try and rebuild it. As soon as it's gone, bingo. Logged in.
They have a bad habit of changing the metadata file formats between releases. Worse, the metadata contains absolute paths so don't, whatever you do, ever try to relocate the directory :-). I've been bitten hard by the situation you describe.
By default, the error messages are not real helpful. If you turn on debugging in the AFP subsystem (see netatalk docs) it will output a detailed trace (you control the granularity). Also, if you run as root you can kick off atalkd under the gdb debugger by telling it not to fork into the background. If built with -g to include symbols you can trace and breakpoint to your heart's content. I become old friends with it while coding the AFP "short name" support eons ago (well, late 90s at any rate).
Here is another thing I noticed about building from the sources. By default, the configure scripts will set the prefix to /usr/local. The netatalk init script will set the path for /usr/local to be priority over the Debian packaged location. If you are in the process of debugging your own built version of netatalk and don't want to lose the originally installed package binaries then 'make install' will override the packaged binaries without removing them. You can back out your built version by deleting the files in /usr/local
I'd actually recommend archiving aside any customized configuration files and uninstalling the Debian package before fooling around with raw sources - regardless of where you install them.
Steve