it would be helpful if testparm(1) could also check for invalid vfs objects listed in the configuration file.
As it is now, smbd will start just fine with anything listed after "vfs objects", and only actually check those names once the share is accessed. Which is fine, as it allows for a dynamic configuration, but testparm could have caught a spelling mistake much sooner.
Created attachment 14439 [details]
testparm issues warning on wrong vfs object names