If ``ceph.conf`` is placed at the default location, which is
``%ProgramData%\ceph\ceph.conf``, then this argument becomes optional.
-The ``-l`` argument also allows using an empty folder as a mountpoint
+The ``-l`` argument also allows using an empty folder as a mount point
instead of a drive letter.
The uid and gid used for mounting the filesystem default to 0 and may be
ceph-dokan.exe unmap -l x
-Note that when unmapping Ceph filesystems, the exact same mountpoint argument
+Note that when unmapping Ceph filesystems, the exact same mount point argument
must be used as when the mapping was created.
Limitations
path to the sub-directory right after "=" in the device part of the mount command.
Mount helper application conventions dictate that the first two options are
-device to be mounted and the mountpoint for that device. Options must be
+device to be mounted and the mount point for that device. Options must be
passed only after these fixed arguments.
| **mount.fuse.ceph** [-h] [-o OPTIONS [*OPTIONS* ...]]
device [*device* ...]
- mountpoint [*mountpoint* ...]
+ mountpoint [*mount point* ...]
Description
===========
Each Ceph cluster has an internal name. This internal name is used as part of
configuration, and as part of "log file" names as well as part of directory
-names and as part of mountpoint names. This name defaults to "ceph". Previous
+names and as part of mount point names. This name defaults to "ceph". Previous
releases of Ceph allowed one to specify a custom name instead, for example
"ceph2". This option was intended to facilitate the running of multiple logical
clusters on the same physical hardware, but in practice it was rarely
driver.
.. note::
- The out-of-tree QAT driver is gradually being migrated to an intree driver+QATlib.
+ The out-of-tree QAT driver is gradually being migrated to an in-tree driver+QATlib.
2. The implementation of QAT-based encryption is directly based on the QAT API,
which is included the driver package. However, QAT support for compression