diff --git a/src/warden-client/doc/README b/src/warden-client/doc/README index 14e1221f1bcb65aa3cd437d4c8921d8698ec5894..fda0e8276a38876a6f4ab42b54fd80e64c2878bf 100644 --- a/src/warden-client/doc/README +++ b/src/warden-client/doc/README @@ -92,12 +92,12 @@ C. Installation (First installation of the Warden client package) are often not accessible by standard users. Install script does check the accessibility of SSL certificates to - provided user. If these files are restricted, the install script will wait - for confirmation. Either privileges to read them must be changed or Warden - client must be run under root. + provided user. If these files are restricted, the install script will raise + a warning. However this will not stop the install process. Either privileges + to read them must be changed or Warden client must be run under root. Of course, after installation of Warden client, SSL certificates may also be - copyied to another location accessible by the user and corresponding paths + copied to another location accessible by the user and corresponding paths changed in warden-client/etc/warden-client.conf. 5. Configuration file @@ -218,11 +218,11 @@ F. Configuration - default set to 6000, which generates app. 250 MB of memory consumption. - only affects "receiving" clients - - Note: server returns the lower number from client's - MAX_RCV_EVENTS_LIMIT and server's internal maximum - size of batch. Contact your Warden server - administrator if you need to know Warden server - batch limits. + + Note: server is queried for the MAX_RCV_EVENTS_LIMIT number of events, + however server can have its own internal maximum size of batch. Contact + your Warden server administrator if you need to know Warden server batch + limits. Since Warden client 2.1 there is also possibility to log status and other information either to STDERR of Syslog.