- If i disable both NFS and SMB i get no errors
- if i enable only NFS (with v4) i get no errors
- if i enable only SMB (or both SMB and NFS) i get the below errors
nas.net.lan root 1885 - - /etc/rc: WARNING: failed to start nfsuserd
nas.net.lan root 1892 - - /etc/rc: WARNING: failed to start mountd
nas.net.lan nfsd 1898 - - Can't read stable storage file: Operation not permitted
nas.net.lan rpc.statd 1900 - - bindresvport_sa: Address already in use
nas.net.lan root 1901 - - /etc/rc: WARNING: failed to start statd
For SMB
- i do not have SMB v1 enabled
- only using ws-discovery - not netbios or mdns
as per one of the other threads, i also see that NFS starts, even if both NFS and SMB are disabled.
Why is it so? Why should should SMB be triggering the startup of nfs?
- if i enable only NFS (with v4) i get no errors
- if i enable only SMB (or both SMB and NFS) i get the below errors
nas.net.lan root 1885 - - /etc/rc: WARNING: failed to start nfsuserd
nas.net.lan root 1892 - - /etc/rc: WARNING: failed to start mountd
nas.net.lan nfsd 1898 - - Can't read stable storage file: Operation not permitted
nas.net.lan rpc.statd 1900 - - bindresvport_sa: Address already in use
nas.net.lan root 1901 - - /etc/rc: WARNING: failed to start statd
For SMB
- i do not have SMB v1 enabled
- only using ws-discovery - not netbios or mdns
as per one of the other threads, i also see that NFS starts, even if both NFS and SMB are disabled.
Why is it so? Why should should SMB be triggering the startup of nfs?
