rdiff-backup-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Rdiff-backup-commits] rdiff-backup CHANGELOG rdiff-backup.1


From: Andrew Ferguson
Subject: [Rdiff-backup-commits] rdiff-backup CHANGELOG rdiff-backup.1
Date: Mon, 21 Jan 2008 21:16:40 +0000

CVSROOT:        /sources/rdiff-backup
Module name:    rdiff-backup
Changes by:     Andrew Ferguson <owsla> 08/01/21 21:16:40

Modified files:
        .              : CHANGELOG rdiff-backup.1 

Log message:
        Manpage updates from Justin Pryzby

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/rdiff-backup/CHANGELOG?cvsroot=rdiff-backup&r1=1.260&r2=1.261
http://cvs.savannah.gnu.org/viewcvs/rdiff-backup/rdiff-backup.1?cvsroot=rdiff-backup&r1=1.86&r2=1.87

Patches:
Index: CHANGELOG
===================================================================
RCS file: /sources/rdiff-backup/rdiff-backup/CHANGELOG,v
retrieving revision 1.260
retrieving revision 1.261
diff -u -b -r1.260 -r1.261
--- CHANGELOG   20 Jan 2008 16:38:11 -0000      1.260
+++ CHANGELOG   21 Jan 2008 21:16:40 -0000      1.261
@@ -1,6 +1,8 @@
 New in v1.1.16 (????/??/??)
 ---------------------------
 
+Manpage improvements from Justin Pryzby.
+
 Improve the handling of directories with many small files when backing-up
 over a network connection. Thanks to Austin Clements for the test case.
 (Andrew Ferguson)

Index: rdiff-backup.1
===================================================================
RCS file: /sources/rdiff-backup/rdiff-backup/rdiff-backup.1,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -b -r1.86 -r1.87
--- rdiff-backup.1      24 Dec 2007 23:01:48 -0000      1.86
+++ rdiff-backup.1      21 Jan 2008 21:16:40 -0000      1.87
@@ -366,11 +366,11 @@
 .B \-\-preserve-numerical-ids
 If set, rdiff-backup will preserve uids/gids instead of trying to
 preserve unames and gnames.  See the
-.B USERS and GROUPS
+.B USERS AND GROUPS
 section for more information.
 .TP
 .B \-\-print-statistics
-If set, summary statistics will be printed after a successful backup
+If set, summary statistics will be printed after a successful backup.
 If not set, this information will still be available from the
 session statistics file.  See the
 .B STATISTICS
@@ -483,7 +483,7 @@
 Map user names and ids according to the user mapping file
 .IR filename .
 See the
-.B USERS and GROUPS
+.B USERS AND GROUPS
 section for more information.
 .TP
 .BI \-v [0-9] ", \-\-verbosity " [0-9]
@@ -644,7 +644,7 @@
 Although ssh itself may be secure, using rdiff-backup in the default
 way presents some security risks.  For instance if the server is run
 as root, then an attacker who compromised the client could then use
-rdiff-backup to overwrite arbitary server files by "backing up" over
+rdiff-backup to overwrite arbitrary server files by "backing up" over
 them.  Such a setup can be made more secure by using the sshd
 configuration option
 .B command="rdiff-backup \-\-server"
@@ -965,7 +965,7 @@
 and
 .B \-\-group-mapping-file
 options override this behavior.  If either of these options is given,
-the policy descriped in 2 and 3 above will be followed, but with the
+the policy described in 2 and 3 above will be followed, but with the
 mapped user and group instead of the original.  If you specify both
 .B \-\-preserve-numerical-ids
 and one of the mapping options, the behavior is undefined.
@@ -1022,7 +1022,7 @@
 but describes every directory backed up.  It also may be compressed to
 save space.
 
-Statistics related options include
+Statistics\-related options include
 .B \-\-print-statistics
 and
 .BR \-\-null-separator .
@@ -1030,7 +1030,7 @@
 Also, rdiff-backup will save various messages to the log file, which
 is rdiff-backup-data/backup.log for backup sessions and
 rdiff-backup-data/restore.log for restore sessions.  Generally what is
-written to this file will coincide with the messages diplayed to
+written to this file will coincide with the messages displayed to
 stdout or stderr, although this can be changed with the
 .B \-\-terminal-verbosity
 option.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]