if you have in a smb.conf section this: vfs objects = foo1 vfs objects = foo2 ...testparm will just output: vfs objects = foo2
At a first glance I would say this is expected behaviour. I always understood the semantics of setting an option more than once such that the later setting overwrites the earlier one. Has this changed from earlier versions, i.e. did 3.5 and before behave differently in this respect? Volker
I was surprised, too. Now that you say it, I had another look and indeed a second "vfs objects" is just evaluated when the first is in the global and the second one is in a share section. Sorry for the noise.