Il giorno lun 23 feb 2015 alle 22:13, Federico Bruni
<[email protected]> ha scritto:
Credo che abbia a che vedere con systemd. Il file .service in debian
è diverso da quello in arch... provo a fare qualche esperimento
ho provato questo:
http://lists.plug.org.au/pipermail/plug/2014-September/083003.html
ma non va:
# systemctl status -l postgresql
● postgresql.service - PostgreSQL database server
Loaded: loaded (/lib/systemd/system/postgresql.service; enabled)
Active: failed (Result: exit-code) since lun 2015-02-23 22:22:30
CET; 1min 48s ago
Process: 22642 ExecStop=/usr/bin/pg_ctl -s -D ${PGROOT}/data stop -m
fast (code=exited, status=203/EXEC)
Process: 22652 ExecStartPre=/usr/bin/postgresql-check-db-dir
${PGROOT}/data (code=exited, status=203/EXEC)
Main PID: 22574 (code=exited, status=0/SUCCESS)
feb 23 22:22:30 laptop systemd[22652]: Failed at step EXEC spawning
/usr/bin/postgresql-check-db-dir: No such file or directory
feb 23 22:22:30 laptop systemd[1]: postgresql.service: control process
exited, code=exited status=203
feb 23 22:22:30 laptop systemd[1]: Failed to start PostgreSQL database
server.
feb 23 22:22:30 laptop systemd[1]: Unit postgresql.service entered
failed state.
