Thanks for the report.

IMHO, The immediate fix would be to have immuos layer use dscl on MacOS. I don't get how service install ever worked on MacOS.

However, I wonder if we can get out of the user management business completely.

• On Linux use systemd DynamicUser (which is what I am doing in this experimental package)
• On MacOS create services by the user installing the service, as we do not expect production workloads here
• On Windows

@padurean @mmeloni what do you think?

@dmacvicar AFAIK running immudb as a service in MacOS never worked. It was assumed no one runs production servers on MacOS, hence the feature is not really needed.

Your suggestions sound good for me, although for Windows we still need to define and decide the approach.

I agree with @dmacvicar & @padurean . We almost never use MacOS for production, it is most likely ubuntu or linux I guess. But we developers might want to setup development environment just like production so that we can consider potential issues might occur when deploying in cloud virtual machine.

It will be easy to fix. https://github.com/codenotary/immudb/tree/master/cmd/sservice is os/customizable .

yep and then https://github.com/codenotary/immudb/tree/master/cmd/immudb/command/service/config

fwiw, just added a service to Homebrew, so users can do:

brew install immudb
brew services start immudb

Ref: Homebrew/homebrew-core#92428

Homebrew

thanks a lot @ankane!