summaryrefslogtreecommitdiff
path: root/textproc/elasticsearch8/files/pkg-message.in
diff options
context:
space:
mode:
Diffstat (limited to 'textproc/elasticsearch8/files/pkg-message.in')
-rw-r--r--textproc/elasticsearch8/files/pkg-message.in43
1 files changed, 43 insertions, 0 deletions
diff --git a/textproc/elasticsearch8/files/pkg-message.in b/textproc/elasticsearch8/files/pkg-message.in
new file mode 100644
index 000000000000..06e0d7d83f64
--- /dev/null
+++ b/textproc/elasticsearch8/files/pkg-message.in
@@ -0,0 +1,43 @@
+[
+{ type: install
+ message: <<EOM
+Please see %%ETCDIR%% for sample versions of
+elasticsearch.yml and logging.yml.
+
+ElasticSearch requires memory locking of large amounts of RAM.
+You may need to set:
+
+sysctl security.bsd.unprivileged_mlock=1
+
+When running within a jail, it's highly advisable to set:
+
+enforce_statfs = 1
+
+for the jail running elasticsearch instance.
+
+NOTICE: elasticsearch port now installs elasticsearch-specific utilities
+as symbolic links into %%BINDIR%%.
+
+!!! PLUGINS NOTICE !!!
+
+ElasticSearch plugins should only be installed via the elasticsearch-plugin
+included with this software. As we strive to provide a minimum semblance
+of security, the files installed by the package are owned by root:wheel.
+This is different than upstream which expects all of the files to be
+owned by the user and for you to execute the elasticsearch-plugin script
+as said user.
+
+You will encounter permissions errors with configuration files and
+directories created by plugins which you will have to manually correct.
+This is the price we have to pay to protect ourselves in the face of
+a poorly designed security model.
+
+e.g., after installing X-Pack you will have to correct:
+
+%%ETCDIR%%/elasticsearch.keystore file to be owned by elasticsearch:elasticsearch
+%%ETCDIR%%/x-pack directory/files to be owned by elasticsearch:elasticsearch
+
+!!! PLUGINS NOTICE !!!
+EOM
+}
+]