FTS Server connections using Samba
FTS Server can run with Linux-hosted filesystems that are local or NFS-mounted. FTS Server can also run with Windows-hosted filesystems mounted on Linux hosts.
Basic Samba configurations
- Allow filesystem sharing.
- Map the Windows user account under which the FTS Server is running to a local Linux account, so that FTS can read and write files under the Samba shares.
- Allow guest access to the Samba shares.
You can find the Samba configuration file that supports the previous description at the following location: /etc/samba/smb.conf.
security = share
username map = </path/to/smb/users/file>
guest ok = yes
guest account = worldserver
Samba examples
map = </path/to/smb/users/file>) associates incoming Windows usernames to local Linux user accounts. To allow FTS access to the files in the Samba shares, the FTS connection must use the same username as the account that WorldServer is running under.
# Unix_name = SMB_name1 SMB_name2 ...
root = administrator admin
worldserver = *
- Windows users "administrator" and "admin" are mapped to the local Linux "root" user.
- Every other Windows user is mapped to the local Linux "worldserver" user.
[mount1]
path = /mnt/ftsAisAssetDir
public = yes
browseable = yes
guest ok = yes
guest only = yes
writable = yes
| [mount1] | Identifies the Samba share that will be visible from a Windows system. |
| path | The actual (local) filesystem folder that contains the assets to be processed. |
| browseable = yes | Allows the share to be seen in a list of available shares. |
| guest ok = yes | Allows connection to the share with no password. |
| guest account = nobody | Specifies the username used for access to the share. |
| guest only = yes | Allows only guest connections to the share (restricts privileges to the defined guest account). |
| writable = yes | Allows the creation of files and folders under the share. |
Local filesystem configuration
- The asset directory associated with the Samba share. For example: /mnt/ftsAisAssetDir
- A top-level directory with the same name as the local host name. For example: mkdir /linuxhost
- A soft link to each Samba share exported by the host – within the top-level host-named folder that points to the physical assets folder. For example: ln -s /mnt/ftsAisAssetDir /linuxhost/mount1
NFS-mounted filesystem configuration
- The NFS server machine (secondlinuxhost, in this example) must export the filesystem (asset directory) to be mounted by remote clients:
share –o rw /export/ftsAssets
- The NFS client machine (linuxhost, in this example) must mount the remote filesystem on the NFS server machine to a local folder. For example:
mount secondlinuxhost:/export/ftsAssets /mnt/ftsAssets
With this configuration, the remote filesystem appears to the local host as a local filesystem. The local filesystem configuration applies, as above, with the following exceptions:
- A top-level folder with the same name as the remote host name must be created, such as:
mkdir /secondlinuxhost
- A soft link to each Samba share exported by the remote host must be created within this top-level folder that maps that Samba share to the local NFS mount corresponding to that share, such as:
ln -s /mnt/ftsAssets /secondlinuxhost/mount2