What is the effect of the copy keyword in a Samba file share configuration?

Question

Options

• AIt includes configuration of another share.
• BIt synchronizes files to another server.
• CIt enables the shadow copy feature.
• DIt creates a copy of each new file in a dedicated path.
• EIt sets the copy mode to enable server-side copies.

• A
  93% (14)
• D
  7% (1)

Explanation

In Samba's smb.conf, the copy parameter lets one share inherit all settings from another named share, acting like a template - so copy = sharename pulls in that share's full configuration block, making A correct.

• B is wrong: Samba's copy has no file synchronization functionality; that would require tools like rsync or DFS.
• C is wrong: Shadow copy (VSS integration) is enabled with vfs objects = shadow_copy2, not the copy keyword.
• D is wrong: No built-in Samba parameter automatically duplicates new files to a secondary path.
• E is wrong: "Server-side copy mode" is not a Samba concept; the parameter simply does not exist in that sense.

Memory tip: Think of copy in smb.conf the way you'd think of "inherits from" in OOP - one share copies the configuration of another share, not the files themselves.

No community discussion yet for this question.