From f4cc12884c91a3edd17fa6a19b8ea4d50226597c Mon Sep 17 00:00:00 2001 From: Pavel Raiskup Date: Wed, 18 Mar 2015 17:37:06 +0100 Subject: sysvinit: initscript & postgresql-setup fixes * postgresql-setup.in($USAGE_STRING): Don't output sysvinit not-relevant options. Generalize the help a bit to match sysvinit. Throw a better warning if user runs 'service initdb postgresql@blah', and, the --port was not passed. In this case, postgresql.conf can't be used. * postgresql.init.in (initdb, upgrade): Add --unit option to postgresql-setup call. --- postgresql.init.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'postgresql.init.in') diff --git a/postgresql.init.in b/postgresql.init.in index dc4c9a7..bf2e9ca 100644 --- a/postgresql.init.in +++ b/postgresql.init.in @@ -187,14 +187,14 @@ __single_comand() initdb() { __single_comand $"Initializing database" \ - @bindir@/@NAME_BINARYBASE@-setup --initdb "$NAME" "$@" + @bindir@/@NAME_BINARYBASE@-setup --initdb --unit "$NAME" "$@" } upgrade() { __single_comand $"Upgrading database" \ - @bindir@/@NAME_BINARYBASE@-setup --upgrade "$NAME" "$@" + @bindir@/@NAME_BINARYBASE@-setup --upgrade --unit "$NAME" "$@" } -- cgit