Bug 9956 - Additional "vfs objects" lines in Samba config invalidates previous lines instead of adding to
Summary: Additional "vfs objects" lines in Samba config invalidates previous lines ins...
Status: RESOLVED DUPLICATE of bug 10641
Alias: None
Product: Samba 3.6
Classification: Unclassified
Component: Config Files (show other bugs)
Version: 3.6.13
Hardware: All All
: P5 minor
Target Milestone: ---
Assignee: Karolin Seeger
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-17 21:59 UTC by Matthew Trent (dead mail address)
Modified: 2021-08-11 20:19 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Trent (dead mail address) 2013-06-17 21:59:10 UTC 
I was experimenting with Samba auditing on my FreeNAS install and added a "vfs object = full_audit" line to a share via FreeNAS's auxiliary options GUI. I found the auditing working, but noticed my share's permissions all whacked out.

After looking at smb.conf, I guessed my extra "vfs objects" line was invalidating the existing default FreeNAS "vfs objects = zfsacl" line, and without zfsacl, permissions were affected. To test, I changed my line to "vfs objects = zfsacl full_audit", and everything worked as expected again.

Obviously a 3rd party product like FreeNAS could/should account for this when building the smb.conf, but given the name "stackable VFS modules", and the lack of any warning about multiple "vfs objects" lines invalidating previous ones, the current behavior could be confusing even for manual smb.conf configuration.
Comment 1 Karolin Seeger 2013-06-27 07:18:38 UTC 
I think this is by design.
When using the the same parameter several times, the last entry is used.
This is very useful in some scenarios.

Closing out bug report.

Thanks!
Comment 2 Björn Jacke 2021-08-11 20:19:41 UTC 

*** This bug has been marked as a duplicate of bug 10641 ***