Netatalk installed with Homebrew doesn't start

[pbobbenb]

Describe the bug
Tried Netatalk from Homebrew, but it can't start because it can't write in the /var/run directory.
This is what is written in the /tmp/netatalk.err file:

netatalk: can't open lock file, "/var/run/netatalk.pid"

If I start it manually from /usr/local/opt/netatalk/sbin/netatalk with sudo everything seems to work fine.

Environment
macOS 14.7.1 and Netatalk 4.0.8 from Homebrew

[rdmark]

Thanks for reporting, and for trying out the formula.

I think this can be addressed by adding this to the install stanza in the formula in the next version: -Dwith-lockfile-path=#{var}/run

This will make netatalk write its lockfile to /opt/homebrew/var/run or aarch, or the Intel equivalent (in my environment: /home/linuxbrew/.linuxbrew/var/run )

@EricFromCanada What do you think?

[EricFromCanada]

@pbobbenb

• Are you running as an admin or a standard user?
• I notice your Homebrew prefix is /usr/local; are you on Intel or ARM?
• What command did you initially run to start the service? In this case, the command would be sudo brew services start netatalk to start it via launchd now and on reboot.
  • You can also run sudo netatalkd start and sudo netatalkd stop
  • First ensure no other netatalk processes are running with Activity Monitor, or your afpd log will fill with errors.

@rdmark Great idea; added.

[pbobbenb]

I'm running as an admin user.
Intel.
It was sudo brew services start netatalk
I tried with netatalkd but it said netatalkd:47: 1: parameter not set
That's why I ran netatalk instead of netatalkd.

[EricFromCanada]

I tried with netatalkd but it said netatalkd:47: 1: parameter not set
That's why I ran netatalk instead of netatalkd.

You need to run sudo netatalkd start and sudo netatalkd stop.

$ sudo netatalkd
/opt/homebrew/bin/netatalkd:47: 1: parameter not set

$ sudo netatalkd start
Starting netatalk fileserver...

[pbobbenb]

Ah, missed that!

[pbobbenb]

Seems to be fixed in v4.1.0.