summaryrefslogtreecommitdiff
path: root/system/zookeeper/README
diff options
context:
space:
mode:
authorB. Watson <yalhcru@gmail.com>2016-11-14 14:51:44 -0500
committerWilly Sudiarto Raharjo <willysr@slackbuilds.org>2016-11-15 21:41:38 +0700
commitdbdfc11563f479eef041d080cc1a53819c2de59e (patch)
tree479825c3460acadb142957125bac045b28a8d7ee /system/zookeeper/README
parent909107ca934ff5496890dee41eabde7842f92dd5 (diff)
downloadslackbuilds-dbdfc11563f479eef041d080cc1a53819c2de59e.tar.gz
system/zookeeper: Fix README.
Diffstat (limited to 'system/zookeeper/README')
-rw-r--r--system/zookeeper/README27
1 files changed, 15 insertions, 12 deletions
diff --git a/system/zookeeper/README b/system/zookeeper/README
index a752f3834e..ed9fb00d94 100644
--- a/system/zookeeper/README
+++ b/system/zookeeper/README
@@ -1,16 +1,19 @@
-ZooKeeper is a centralized service for maintaining configuration information,
-naming, providing distributed synchronization, and providing group services.
-All of these kinds of services are used in some form or another by distributed
-applications. Each time they are implemented there is a lot of work that goes
-into fixing the bugs and race conditions that are inevitable. Because of the
-difficulty of implementing these kinds of services, applications initially
-usually skimp on them ,which make them brittle in the presence of change and
-difficult to manage. Even when done correctly, different implementations of
-these services lead to management complexity when the applications are
-deployed.
+ZooKeeper is a centralized service for maintaining configuration
+information, naming, providing distributed synchronization, and providing
+group services.
-This script requires a 'zookeeper' user/group to exist before running.
+All of these kinds of services are used in some form or another by
+distributed applications. Each time they are implemented there is a
+lot of work that goes into fixing the bugs and race conditions that
+are inevitable. Because of the difficulty of implementing these kinds
+of services, applications initially usually skimp on them ,which make
+them brittle in the presence of change and difficult to manage. Even
+when done correctly, different implementations of these services lead
+to management complexity when the applications are deployed.
+
+This script requires a 'zookeeper' user/group to exist before running.
The recommended UID/GID is 322. You can create these like so:
groupadd -g 322 zookeeper
-useradd -u 322 -g 322 -c "Zookeeper user" -d /var/lib/zookeeper -s /bin/sh zookeeper
+useradd -u 322 -g 322 -c "Zookeeper user" \
+ -d /var/lib/zookeeper -s /bin/sh zookeeper