summaryrefslogtreecommitdiff
path: root/databases/slony1v2/files/pkg-message.in
diff options
context:
space:
mode:
Diffstat (limited to 'databases/slony1v2/files/pkg-message.in')
-rw-r--r--databases/slony1v2/files/pkg-message.in19
1 files changed, 12 insertions, 7 deletions
diff --git a/databases/slony1v2/files/pkg-message.in b/databases/slony1v2/files/pkg-message.in
index 1cf868e2de69..83bce1b71a05 100644
--- a/databases/slony1v2/files/pkg-message.in
+++ b/databases/slony1v2/files/pkg-message.in
@@ -1,13 +1,11 @@
-*******************************************************************************
-
+[
+{ type: install
+ message: <<EOM
Please read the docs on configuring and running slony-1.
Unless you did not specify the DOCS options, they are in the
%%LOCALBASE%%/share/doc/slony1v2 directory.
-If you are upgrading from a prior version of slony, please read the UPGRADING
-file in the above docs directory.
-
The script %%LOCALBASE%%/sbin/slon-mkservice can be used to create a control
directory to run and monitor the slon daemon under svscan from daemontools.
If you use this, be sure not to set slon_enable="YES" in /etc/rc.conf.
@@ -21,5 +19,12 @@ is documented in %%LOCALBASE%%/share/doc/slony1/adminguide/runtime-config.html
%%PERLTOOLS%%
%%PERLTOOLS%%To use the perl slony configuration and monitoring tools, you must
%%PERLTOOLS%%create %%LOCALBASE%%/etc/slon_tools.conf based on the sample file.
-
-*******************************************************************************
+EOM
+}
+{ type: upgrade
+ message: <<EOM
+If you are upgrading from a prior version of slony, please read the UPGRADING
+file in the above docs directory.
+EOM
+}
+]