Novell IFOLDER 3.7 - SECURITY ADMINISTRATION, Руководство администратора

Страница: 32 / 216

32 OES 2 SP1: Novell iFolder 3.7 Administration Guide
no
vd
ocx
(e
n)
13
Ma
y 20
09
Š
Names of iFolders, folders, and files are case insensitive; however, case is preserved. If
filenames differ only by case, iFolder creates a name conflict. The conflict must be resolved
before the file or folder can be synchronized.
Š
If users create iFolders on the FAT32 file system on Linux, they should avoid naming files in all
uppercase characters. The VFAT or FAT32 file handling on Linux automatically changes the
filenames that are all uppercase characters and meet the MS-DOS 8.3 file format from all
uppercase characters to all lowercase characters. This creates synchronization problems for
those files if the iFolder is set with the Read Only access right.
2.6.2 Guidelines for File Types and Sizes to Be Synchronized
You can set policies to govern which files are synchronized by specifying file type restrictions and
the maximum file size allowed to be synchronized. You can set these policies at the system, user
account, and iFolder level.
Some file types are not good candidates for synchronization, such as operating system files, hidden
files created by a file manager, or databases that are implemented as a collection of linked files. You
might include only key file types used for your business, or exclude files that are likely unrelated to
business, such as
.mp3
files.
Operating System Files
You should not convert system directories to iFolders. Most system files change infrequently and it
is better to keep an image file of your basic system and key software than to attempt to synchronize
those files to the server.
Hidden Files
If your file system uses hidden files to track display preferences, you should determine the file types
of these files and exclude them from being synchronized on your system. Usually, they are relevant
only to the particular computer where they were created, and they change every time the file or
directory is accessed. You do not need to keep these files, and synchronizing them results in repeated
file conflict errors.
For example, iFolder automatically excludes two hidden file manager files called
thumbs.db
and
.DS_Store
.
Database Files
iFolder synchronizes the changed portions of a file; it does not synchronize files as a set. If you have
a database file that is implemented as a collection of linked files, do not try to synchronize them in
an iFolder.
Do not try to synchronize your GroupWise
®
data by making the GroupWise archive, cache, or
remote directories into iFolders. If you do this, the GroupWise data files becomes corrupted after
synchronizing the file a few times. GroupWise needs the files in the archive to be maintained as a set
of files.