-The CNID backends maintains name to ID mappings. If you change a
-filename outside afpd(8) (shell, samba), the CNID db, i.e. the DIDNAME
-index, gets inconsistent. Netatalk tries to recover from such
-inconsistencies as gracefully as possible. The mechanisms to resolve such
-inconsistencies may fail sometimes, though, as this is not an easy task to
-accomplish. I.e. if several names in the path to the file or directory
-have changed, things may go wrong.
-.PP
-If you change a lot of filenames at once, chances are higher that
-the afpds fallback mechanisms fail, i.e. files will be assigned new IDs,
-even though the file hasn't changed. uniconv
-therefore updates the CNID entry for each file/directory directly after it
-changes the name to avoid inconsistencies. The two supported backends for
-volumes, dbd and cdb, use the same CNID db format. Therefore, you
-\fIcould\fR use uniconv with cdb and
-afpd with dbd later.
-.PP
-\fBWarning\fR: There must not be two
-processes opening the CNID database using different backends at once! If a
-volume is still opened with dbd (cnid_metad/cnid_dbd) and you start
-uniconv with cdb, the result will be a corrupted CNID
-database, as the two backends use different locking schemes. You might run
-into additional problems, e.g. if dbd is compiled with transactions, cdb
-will not update the transaction logs.
+.PP
+The CNID backends maintains name to ID mappings\&. If you change a filename outside afpd(8) (shell, samba), the CNID db, i\&.e\&. the DIDNAME index, gets inconsistent\&. Netatalk tries to recover from such inconsistencies as gracefully as possible\&. The mechanisms to resolve such inconsistencies may fail sometimes, though, as this is not an easy task to accomplish\&. I\&.e\&. if several names in the path to the file or directory have changed, things may go wrong\&.
+.PP
+If you change a lot of filenames at once, chances are higher that the afpds fallback mechanisms fail, i\&.e\&. files will be assigned new IDs, even though the file hasn\'t changed\&.
+\fBuniconv\fR
+therefore updates the CNID entry for each file/directory directly after it changes the name to avoid inconsistencies\&. The two supported backends for volumes, dbd and cdb, use the same CNID db format\&. Therefore, you
+\fIcould\fR
+use
+\fBuniconv\fR
+with cdb and
+\fBafpd\fR
+with dbd later\&.
+.PP
+\fBWarning\fR: There must not be two processes opening the CNID database using different backends at once! If a volume is still opened with dbd (cnid_metad/cnid_dbd) and you start
+\fBuniconv\fR
+with cdb, the result will be a corrupted CNID database, as the two backends use different locking schemes\&. You might run into additional problems, e\&.g\&. if dbd is compiled with transactions, cdb will not update the transaction logs\&.