Netatalk 4.0 - Future-proofing Apple File Sharing

[Slimes]

@Slimes Did you recall what your afp.conf looked like before? You only added "log file" and nothing else? If you comment out "log file" and try again, does the crash make a return?

When it was crashing, how frequently did you see the crash? Was is intermittent, or fully deterministic and triggered by specific actions?

Only change were the log lines. I would roll back but im actively using it right now.
crashing was every 30 to 60 seconds after connecting from os9.2 quicksilver chooser.

been over 12 hours now, many gigs transferred. No issues.

more details server side
crashing existed with:
both wired and wireless
macOS sharing smb on and off
no apps open, or some apps open

The only deterministic factor was the log config entries. Installed via homebrew.

btw, thanks for netatalk. massive improvement over ftp.

 

[Slimes]

Is there a tutorial on how to make netatalk a Launchdaemon? I’ve tried the official “new” way but I can’t seem to get it to work.
macOS 26.

 

[rdmark]

Is there a tutorial on how to make netatalk a Launchdaemon? I’ve tried the official “new” way but I can’t seem to get it to work.
macOS 26.

Can you please describe the official new way that you tried? To my best knowledge launchd didn't significantly change in macOS Tahoe but I could be missing some detail.

If it doesn't get built by default for some reason, you can force the netatalk build system to install the launchd files with "-Dwith-init-style=macos-launchd".

The netatalk wiki has a page that describes how to start netatalk with launchd: https://github.com/Netatalk/netatalk/wiki/Installing-Netatalk-on-macOS

Please let me know if any of this information is outdated!

 

[rdmark]

As a side note, I filed the macOS crash bug as https://github.com/Netatalk/netatalk/issues/2452 so that we can try to figure out what's causing it. The callstack suggests that that the crash is in the afp_flush() function.

 

[Slimes]

As a side note, I filed the macOS crash bug as https://github.com/Netatalk/netatalk/issues/2452 so that we can try to figure out what's causing it. The callstack suggests that that the crash is in the afp_flush() function.

'new' way tutorial. Its complicated.

launchctl “new” subcommand basics for macOS – Alan Siu's Blog

 

[rdmark]

'new' way tutorial. Its complicated.

launchctl “new” subcommand basics for macOS – Alan Siu's Blog

I don't think you need to care about all that. The "system/io.netatalk.daemon" service just needs to be enabled, after which the netatalk daemons will start up automatically on system boot. The meson build system should set it up for you by default. But if you for instance run "launchctl print system" and don't see io.netatalk.daemon listed as an enabled service, you can run the enable command manually:

sudo launchctl enable system/io.netatalk.daemon

If you're still having problems, please share the output of "launchctl print system" and have a look in the Console app if launchd is posting any errors there.

 

[Slimes]

The netatalk daemon is enabled, however, it doesn't launch netatalkd on system startup.

No errors. No faults.