diff options
| author | Pawel Jakub Dawidek <pjd@FreeBSD.org> | 2010-07-22 08:30:14 +0000 |
|---|---|---|
| committer | Pawel Jakub Dawidek <pjd@FreeBSD.org> | 2010-07-22 08:30:14 +0000 |
| commit | 1a517c3ec572555fe09cdcb5f0e68749953c0b83 (patch) | |
| tree | 166b32e26cadc4faf9b9be430325f6ca16b499e1 /sbin | |
| parent | 175389cff2201de51f3743cf4029a77359e55dc4 (diff) | |
| download | src-1a517c3ec572555fe09cdcb5f0e68749953c0b83.tar.gz src-1a517c3ec572555fe09cdcb5f0e68749953c0b83.zip | |
Actually, only the fullsync mode is implemented, not memsync mode.
Correct manual page.
MFC after: 3 days
Notes
Notes:
svn path=/head/; revision=210368
Diffstat (limited to 'sbin')
| -rw-r--r-- | sbin/hastd/hast.conf.5 | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/sbin/hastd/hast.conf.5 b/sbin/hastd/hast.conf.5 index 691448d4fe48..5377e6abdc55 100644 --- a/sbin/hastd/hast.conf.5 +++ b/sbin/hastd/hast.conf.5 @@ -175,8 +175,10 @@ Before secondary node returns, primary node dies entirely. When the secondary node comes back to life it becomes the new primary. Unfortunately some small amount of data which was confirmed to be stored to the application was lost. -The risk of such a situation is very small, which is the reason for this -mode to be the default. +The risk of such a situation is very small. +The +.Ic memsync +replication mode is currently not implemented. .It Ic fullsync .Pp Mark the write operation as completed when local as well as remote @@ -184,7 +186,7 @@ write completes. This is the safest and the slowest replication mode. The .Ic fullsync -replication mode is currently not implemented. +replication mode is the default. .It Ic async .Pp The write operation is reported as complete right after the local write |