Error in syslog at startup

[nemihome]

Hi, not sure if I'm doing something wrong:
ERROR: Unable to create /etc/ksmbd/ksmbd.subauth.tmp: Permission denied

I also tried to create the file with rights of the user starting ksmbd but that is resulting in an error message file already exists.

Im on Ubuntu 22.04

[namjaejeon]

You need to run ksmbd.mountd with root permission. there is no the other permission under /etc/.
or replace smb.conf location with other user directory using --c option.

[nemihome]

Hi, thank you for the answer. I used sudo but did not logon with root byself. Did that now. Basically it seems to be running now.

Problems which I do have at the moment:

• Symlinks as path do not work completely. If I use symlinks it is possible to write to the path, it is possible to edit files, change their name. But as soon as I try do download them I will run into an error 0x8007045D on Win 10 / 11. So basically the symlinks are working partially.
• Hosts allow with the classic smb format does not work:
  hosts allow 10.8.0.0/24 127.0.0.1 192.168.179.1/24 192.168.179.2/24 192.168.179.3/24 192.168.178.24/24 192.168.178.37/24 192.168.178.27/24 192.168.178.25/24 192.168.178.35/24 192.168.178.54/24 192.168.178.34/24 192.168.178.43/24 192.168.178.45/24 192.168.178.20/24 192.168.178.52/24 192.168.178.42/24 192.168.178.43/24 192.168.178.44/24
  I also tried just one IP 192.168.179.1 or host name from host file but as soon as I use this it is not working.
  What format is needed for that? Help: "This parameter is a comma, space, or tab delimited set of hosts which are permitted to access a service" Well there are spaces but even with one ip, host it does not seem to be working.

Feature request:
Is there a chance that:
follow symlinks = yes
wide links = yes
will be supported in future?

I know that wide links option is insecure but I have around 27TB of iso files on my NAS and biggest drives are 20TB at the moment. So I used symlinks to have all files virtually on one harddisc. Another option would be to create a virtual drive (combining two physical drives) but with higher risc of failure (loosing both when loosing one).

The config file is extremely sensitive for spaces behind a line which is not the case for old samba config. This seems to be handled line by line. After purging the file it worked better

I think documentation of config file could be improved a little bit with some examples. ;) Apart from that good work, seems to be faster based on first tests. So if hosts allow and symlinks whould work I will thing about chaning to ksmbd instead of using classic samba.