mirror of
https://github.com/unraid/webgui.git
synced 2026-01-24 18:49:17 -06:00
smb: add case-sensitiviy config setting per share
This commit is contained in:
@@ -92,6 +92,32 @@ Time Machine volume size limit:
|
||||
> This limits the reported volume size, preventing Time Machine from using the entire real disk space
|
||||
> for backup. For example, setting this value to "1024" would limit the reported disk space to 1GB.
|
||||
|
||||
<?endif;?>
|
||||
<?if ($name != 'flash'):?>
|
||||
Case-sensitive names:
|
||||
: <select name="shareCaseSensitive" size="1">
|
||||
<?=mk_option($sec[$name]['caseSensitive'], "auto", "Auto");?>
|
||||
<?=mk_option($sec[$name]['caseSensitive'], "yes", "Yes");?>
|
||||
<?=mk_option($sec[$name]['caseSensitive'], "forced", "Force lower");?>
|
||||
</select>
|
||||
|
||||
> Controls whether filenames are case-sensitive.
|
||||
>
|
||||
> The default setting of **auto** allows clients that support case sensitive filenames (Linux CIFSVFS)
|
||||
> to tell the Samba server on a per-packet basis that they wish to access the file system in a case-sensitive manner (to support UNIX
|
||||
> case sensitive semantics). No Windows system supports case-sensitive filenames so setting this option to **auto** is the same as
|
||||
> setting it to No for them; however, the case of filenames passed by a Windows client will be preserved. This setting can result
|
||||
> in reduced peformance with very large directories because Samba must do a filename search and match on passed names.
|
||||
>
|
||||
> A setting of **Yes** means that files are created with the case that the client passes, and only accessible using this same case.
|
||||
> This will speed very large directory access, but some Windows applications may not function properly with this setting. For
|
||||
> example, if "MyFile" is created but a Windows app attempts to open "MYFILE" (which is permitted in Windows), it will not be found.
|
||||
>
|
||||
> A value of **Forced lower** is special: the case of all incoming client filenames, not just new filenames, will be set to lower-case.
|
||||
> In other words, no matter what mixed case name is created on the Windows side, it will be stored and accessed in all lower-case. This
|
||||
> ensures all Windows apps will properly find any file regardless of case, but case will not be preserved in folder listings.
|
||||
> Note this setting should only be configured for new shares.
|
||||
|
||||
<?endif;?>
|
||||
Security:
|
||||
: <select name="shareSecurity" size="1">
|
||||
|
||||
Reference in New Issue
Block a user