NFS Service Starts Automatically on reboot when not selected to do so

12.0 PR: https://github.com/truenas/middleware/pull/7760

 this is brilliant. The binding to an IP address was the information that I needed. I was able to reproduce the problem. I'll be pushing a fix.

- I was also able to recreate this on my backup box... this appears to be a bug.

: I have done some more troubleshooting and can successfully fix and then recreate the issue. I found that in my settings for the NFS service, I was selected to bind to 1 of my 2 network interfaces.  When I removed that binding (default to all by not selecting any), I could restart the box and NFS would not restart.  If I went back in and selected 1 of the interfaces, the service auto starts at next reboot, regardless of the GUI setting for auto start.  So my fix is to uncheck both of my interfaces from the bind selection, and now I can reboot without the NFS service automatically starting.  I would see if you are able to recreate this on your end... It seems that by editing the bind option to something other than default, the service automatically starts for me at reboot time.... this might be my box due to some configuration I previously had, or it might be a bug.

To answer your question, I was just referring to the GUI, so I ran this in the shell to confirm nfsd was running:

and this was the result:

, thanks for the reply. So I've been trying to reproduce this in-house every which way and I can't seem to reproduce this problem. When you reboot your box, how are you confirming that the service is running? Are you confirming via the CLI or is the webUI showing the service started?