From 6b3ef14a652f6be0d559365d2fd2c78a61524fec Mon Sep 17 00:00:00 2001
From: matthew_swift <matthew_swift@localhost>
Date: Fri, 17 Sep 2010 22:06:25 +0000
Subject: [PATCH] Minimize Historical Data (dsreplication/client side). The purge historical can be executed on the local server even when it is stopped. This is matches the functionality provided by utilities such import-ldif, backup, etc.

---
 opends/src/messages/messages/tools.properties |   19 +++++++++++++------
 1 files changed, 13 insertions(+), 6 deletions(-)

diff --git a/opends/src/messages/messages/tools.properties b/opends/src/messages/messages/tools.properties
index de2e120..59203c0 100644
--- a/opends/src/messages/messages/tools.properties
+++ b/opends/src/messages/messages/tools.properties
@@ -674,7 +674,8 @@
  restarted
 INFO_STOPDS_DESCRIPTION_STOP_TIME_384=Indicates the date/time at which the \
  shutdown operation will begin as a server task expressed in format \
- 'YYYYMMDDhhmmss'.  A value of '0' will cause the shutdown to be scheduled for \
+ YYYYMMDDhhmmssZ for UTC time or YYYYMMDDhhmmss for local time.  A value of \
+ '0' will cause the shutdown to be scheduled for \
  immediate execution.  When this option is specified the operation will be \
  scheduled to start at the specified time after which this utility will exit \
  immediately
@@ -2153,13 +2154,14 @@
 SEVERE_ERR_TASK_CLIENT_TASK_STATE_UNKNOWN_1455=State for task '%s' cannot be \
   determined
 INFO_DESCRIPTION_START_DATETIME_1456=Indicates the date/time at which this \
-  operation will start when scheduled as a server task expressed in format \
-  'YYYYMMDDhhmmss'.  A value of '0' will cause the task to be scheduled for \
+  operation will start when scheduled as a server task expressed in \
+  YYYYMMDDhhmmssZ format for UTC time or YYYYMMDDhhmmss for local time.  A \
+  value of '0' will cause the task to be scheduled for \
   immediate execution.  When this option is specified the operation will be \
   scheduled to start at the specified time after which this utility will exit \
   immediately
-SEVERE_ERR_START_DATETIME_FORMAT_1457=The start date/time must in format \
-  'YYYYMMDDhhmmss'
+SEVERE_ERR_START_DATETIME_FORMAT_1457=The start date/time must in \
+  YYYYMMDDhhmmssZ format for UTC time or YYYYMMDDhhmmss for local time
 INFO_TASK_TOOL_TASK_SCHEDULED_FUTURE_1458=%s task %s scheduled to start %s
 SEVERE_ERR_TASK_TOOL_START_TIME_NO_LDAP_1459=You have provided options for \
   scheduling this operation as a task but options provided for connecting to \
@@ -2574,4 +2576,9 @@
 SEVERE_ERR_CLIENT_SIDE_TIMEOUT_1714=A client side timeout occurred.\
  %nAdditional Information:  %s
 INFO_LABEL_DBTEST_INDEX_UNDEFINED_RECORD_COUNT_1715=Undefined
-
+INFO_MAXIMUM_DURATION_PLACEHOLDER_1716={maximum duration}
+INFO_DESCRIPTION_PURGE_HISTORICAL_MAXIMUM_DURATION_1717=This argument specifies \
+the maximum duration the purge processing must last expressed in seconds
+SEVERE_ERR_RECURRING_SCHEDULE_FORMAT_ERROR_1718=The provided schedule value \
+ has an invalid format.  The schedule must be expressed using a crontab(5) \
+ format.  Error details: %s

--
Gitblit v1.10.0