@robin-fo Version 4.0.8 is tagged now, that contains the build system fix for not linking with LDAP.framework, if Homebrew openldap is available.
https://netatalk.io/4.0/ReleaseNotes4.0.8
The recommended Homebrew packages are dynamically kept up to date in the manual...
This seems to do the trick. If the Homebrew openldap library is present, it will be used by default now.
https://github.com/Netatalk/netatalk/pull/1792
Eventually, I want to remove the "OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES" workaround from the netatalkd script, but not in the stable 4.0...
Look at that, Apple’s docs corroborate this assertion. (Table A-1)
https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/OSX_Technology_Overview/SystemFrameworks/SystemFrameworks.html
Good thing we had this conversation! Let me tweak the build system to favor openldap on...
Thanks for your feedback!
Do you mean moving the "Show Server Status" link to the default tab (File Sharing Services), and keeping the rest under Global Settings, correct?
I can see how that would make sense, in that a user would want to check the AFP server's response on the same page that...
According to otool, the macOS system libraries we link with are: libSystem, libiconv and LDAP.framework.
otool -L libatalk.19.dylib
libatalk.19.dylib:
@rpath/libatalk.19.dylib (compatibility version 19.0.0, current version 19.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0...
While I don't think this will make a big difference for your issues, this inspired me to apply the other workaround supplied by Apple: To instruct the linker to inject a section in the compiled binary with the contents "__DATA,__objc_fork_ok".
I have implemented and tested it in the PR below...
What tooling to you use for debugging on macOS? Even on Linux, following forking processes in gdb is hit and miss in my experience. There might be a trick that I'm missing.
Are you not able to use the "OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES" env variable workaround when developing? The article...
I was thinking about this forking situation again recently. Pardon me if this discussed this in detail in a different thread and I forgot about it, but I would like to know more about how afpd's process forking is making your effort in writing a userspace AppleTalk stack more difficult.
Using...
@Mk.558 I had the inspiration to fiddle with the webmin module this morning. Can you please give me feedback on this approach to a tabbed interface?
I thought about making the tabbed interface even more radically flat (f.e. exploding all global settings into top level tabs) however this would...
I struggled with the debugclass option too. There's some binary arithmetic going on in main.c that I don't quite understand. But Jason's macipgw wiki page thankfully has a useful example that I have applied with success.
Quoting:
Thanks for sharing your upgrade story! I'm still kind of amazed that you all are having a relatively smooth ride moving from 2.x to 4.0. :)
So afppasswd is a little rough around the edges perhaps. Not the most user friendly app. The flow goes something like this:
- The root user runs...
I see what you're saying. The reason for not enabling the Webmin module by default is primarily a technical one, to do with my lack of skill with Meson scripting. I'm using a dirty workaround that leverages absolute paths in the build dirs to create and access the Webmin module distribution...
Thanks for sharing your success story! What was your approach to upgrading the container? Did you just swap out the image in a docker-compose file and that was it?
Nice catch. I pushed a fix to the main branch. The html manual will get updated when I publish the next bugfix release.
Included where, you mean? The with-webmin Meson option will attempt to detect if Webmin is installed on your system, and if found will package and install the wbm tarball for...
@saybur This should address the gaps in the manual that you encountered. Please let me know if you have other improvement ideas.
https://github.com/Netatalk/netatalk/pull/1609
Conceptually the two do appear mutually exclusive. I think ideally, they should be combined into one option, with the code detecting whether you specify an interface name or IP addresses.
But for starters, I agree the afp.conf man page should be updated.
Good call-out. I think it's also...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.