diff --git a/doc/generated/libpmemblk.7 b/doc/generated/libpmemblk.7 index e2d5f2a898a039405d156f7c4fb78ceb8e59aa8f..ee1d47be9325b1a9381ca61b8d76a21f50acd663 100644 --- a/doc/generated/libpmemblk.7 +++ b/doc/generated/libpmemblk.7 @@ -1,6 +1,6 @@ .\" Automatically generated by Pandoc 2.0.6 .\" -.TH "LIBPMEMBLK" "7" "2019-10-03" "PMDK - pmemblk API version 1.1" "PMDK Programmer's Manual" +.TH "LIBPMEMBLK" "7" "2019-10-10" "PMDK - pmemblk API version 1.1" "PMDK Programmer's Manual" .hy .\" Copyright 2014-2019, Intel Corporation .\" @@ -98,7 +98,7 @@ blocks, all the same size, where any given block is updated atomically (the update cannot be \f[I]torn\f[] by program interruption such as power failures). This library builds on the low\-level pmem support provided by -\f[B]libpmem\f[](3), handling the transactional update of the blocks, +\f[B]libpmem\f[](7), handling the transactional update of the blocks, flushing to persistence, and recovery for the application. \f[B]libpmemblk\f[] is one of a collection of persistent memory libraries available, the others are: diff --git a/doc/generated/pmemlog_append.3 b/doc/generated/pmemlog_append.3 index bdf8c8e1db9558a446bdfa35398c8771b0161a19..7bd182ed85093536dbb7ab366770187589eb8c95 100644 --- a/doc/generated/pmemlog_append.3 +++ b/doc/generated/pmemlog_append.3 @@ -1,6 +1,6 @@ .\" Automatically generated by Pandoc 2.0.6 .\" -.TH "PMEMLOG_APPEND" "3" "2019-07-10" "PMDK - pmemlog API version 1.1" "PMDK Programmer's Manual" +.TH "PMEMLOG_APPEND" "3" "2019-10-10" "PMDK - pmemlog API version 1.1" "PMDK Programmer's Manual" .hy .\" Copyright 2014-2019, Intel Corporation .\" @@ -75,7 +75,7 @@ On error, they return \-1 and set \f[I]errno\f[] appropriately. \f[B]EROFS\f[] The log file is open in read\-only mode. .SH NOTES .PP -Since \f[B]libpmemlog\f[](3) is designed as a low\-latency code path, +Since \f[B]libpmemlog\f[](7) is designed as a low\-latency code path, many of the checks routinely done by the operating system for \f[B]writev\f[](2) are not practical in the library's implementation of \f[B]pmemlog_appendv\f[](). diff --git a/doc/generated/poolset.5 b/doc/generated/poolset.5 index 1343bd81607bd0a0ff8b07f56e4f9f4170eb8e2d..0bb2570cd662ff2ada1af8a60e4828021d6bd0ea 100644 --- a/doc/generated/poolset.5 +++ b/doc/generated/poolset.5 @@ -1,6 +1,6 @@ .\" Automatically generated by Pandoc 2.0.6 .\" -.TH "POOLSET" "5" "2019-07-10" "PMDK - poolset API version 1.0" "PMDK Programmer's Manual" +.TH "POOLSET" "5" "2019-10-10" "PMDK - poolset API version 1.0" "PMDK Programmer's Manual" .hy .\" Copyright 2014-2019, Intel Corporation .\" @@ -202,7 +202,7 @@ REPLICA\ [<user>\@]<hostname>\ [<relative\-path>/]<remote\-pool\-set\-file> \f[B]ssh\f[](1) remote login client .IP \[bu] 2 \f[I]pathname\f[] is relative to the root config directory on the target -node \- see \f[B]librpmem\f[](3) +node \- see \f[B]librpmem\f[](7) .PP There are no other lines in the remote replica section \- the REPLICA line defines a remote replica entirely. @@ -320,11 +320,11 @@ using the \f[B]pmempool\f[](1) utility. .PP Restoring data from a local or remote replica can be done by using the \f[B]pmempool\-sync\f[](1) command or the \f[B]pmempool_sync\f[]() API -from the \f[B]libpmempool\f[](3) library. +from the \f[B]libpmempool\f[](7) library. .PP Modifications of a pool set file configuration can be done by using the \f[B]pmempool\-transform\f[](1) command or the -\f[B]pmempool_transform\f[]() API from the \f[B]libpmempool\f[](3) +\f[B]pmempool_transform\f[]() API from the \f[B]libpmempool\f[](7) library. .PP When creating a pool set consisting of multiple files, or when creating