| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
We need to create both files separately as (a) the
'postgresql.service' can not .include 'postgresql@.service' for
some reason, /usr/lib/ drop-in breaks things (rhbz#1141824) and
we want to have PGDATA unset for postgresql@.service, unlike the
postgresql.service file.
|
| |
|
|
|
|
|
|
| |
That concept was against systemd intentions. From now we
should stop using .include statement in service files and
encourage people using the systemd's drop-in feature. That
complicates things a little, at least until the rhbz#1139148
is not resolved somehow.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If user removes currently provided /etc/postgresql/postgresql
configuration file, PGDATA env variable is not set. The
`systemctl start postgresql` would fail similarly to
`systemctl start postgresql@NOTCONFIGURED` when the configuration
file was not created yet with cryptic message
"Usage: ... "
Stop this behavior rather explicitly with proper error in
check-db-dir script.
Warn also user in similar fashion that the configuration should be
adjusted in case the PGDATA was set directly in service file.
|
| |
|
|
|
|
|
|
| |
The %N expands into postgresql@PATTERN when you run
systemctl start postgresql@PATTERN.service. The %p expanded only
to "postgresql".
Also make the existance of this file optional by dash-prefixing.
|
| |
|
|
|
| |
Also generate files using sed as is suggested by autoconf manual
(and the autoconf project does so internally).
|
| |
|
