[ Pobierz całość w formacie PDF ]
.For example, if you veWe recommend that you leave this option alone unless you have a well-justifiedused Windows 95/98/NT, you have likely run across a file called README.TXT.need to change it.The file can be represented by the operating system entirely in uppercase letters.However, if you open an MS-DOS prompt and enter the command edit readme.mangling chartxt, the all-caps file is loaded into the editing program, even though you typedthe name in lowercase letters!This share-level option specifies the mangling character used when Samba man-gles filenames into the 8.3 format.The default character used is a tilde (~).YouThis is because the Windows 95/98/NT family of operating systems resolves filescan reset it to whatever character you wish, for instance:in a case-insensitive manner, even though the files are represented it in a case-[data] sensitive manner.Unix-based operating systems, on the other hand, always resolvemangling char = #files in a case-sensitive manner; if you try to edit README.TXT with the commandvireadme.txt, you will likely be editing the empty buffer of a new file.mangled stackHere is how Samba handles case: if the preserve case is set to yes, Samba willSamba maintains a local stack of recently mangled 8.3 filenames; this stack can bealways use the case provided by the operating system for representing (not resolv-used to reverse map mangled filenames back to their original state.This is oftening) filenames.If it is set to no, it will use the case specified by the defaultcaseneeded by applications that create and save a file, close it, and need to modify itoption.The same is true for short preserve case.If this option is set to yes,later.The default number of long filename/mangled filename pairs stored on thisSamba will use the default case of the operating system for representing 8.3stack is 50.However, if you want to cut down on the amount of processor timefilenames; otherwise it will use the case specified by the default case option.used to mangle filenames, you can increase the size of the stack to whatever youFinally, Samba will always resolve filenames in its shares based on the value of thewish, at the expense of memory and slightly slower file access.casesensitive option.[global]mangled stack = 100Mangling Optionsmangled mapSamba allows you to give it more refined instructions on how it should performIf the default behavior of name mangling is not sufficient, you can give Samba fur-name mangling, including those controlling the case sensitivity, the characterther instructions on how to behave using the mangled map option.This optioninserted to form a mangled name, and the ability to manually map filenames fromallows you to specify mapping patterns that can be used before or even in placeone format to another.These options are shown in Table 5-7.of name mangling performed by Samba.For example:Table 5-7.Name Mangling Options[data]mangled map =(*.database *.db) (*.class *.cls) Option Parameters Function Default Scopecase sensitive boolean If yes, Samba will treat file- no ShareHere, Samba is instructed to search each file it encounters for characters that(casesignames) names as case-sensitivematch the first pattern specified in the parenthesis and convert them to the modi-(Windows doesn t).fied second pattern in the parenthesis for display on an 8.3 client.This is useful indefault case (upper or Case to assume as default Lower Sharelower) (only used when preservecase is no). 152 Chapter 5: Browsing and Advanced Disk Shares Locks and Oplocks 149The sharemodes parameter, which enforces the use of these locks, is enabled by the event that name mangling converts the filename incorrectly or to a format thatdefault.To disable it, use the following command: the client cannot understand readily.Patterns are separated by whitespaces.[accounting]share modes = noLocks and OplocksWe highly recommend against disabling the default locking mechanism unless youConcurrent writes to a single file are not desirable in any operating system.Tohave a justifiable reason for doing so.Most Windows and DOS applications relyprevent this, most operating systems use locks to guarantee that only one processon these locking mechanisms in order to work correctly, and will complain bit-can write to a file at a time.Operating systems traditionally lock entire files,terly if this functionality is taken away.although newer ones allow a range of bytes within a file to be locked.If anotherprocess attempts to write to a file (or section of one) that is already locked, it willlockingreceive an error from the operating system and will wait until the lock is released.The lockingoption can be used to tell Samba to engage or disengage server-sideSamba supports the standard DOS and NT filesystem (deny-mode) lockingbyte-range locks on behalf of the client
[ Pobierz całość w formacie PDF ]