From mboxrd@z Thu Jan 1 00:00:00 1970 From: Catonano Subject: bug#29992: 'postgres' service doesn't stop Date: Fri, 12 Jan 2018 10:46:08 +0100 Message-ID: References: <87mv1scodq.fsf@lassieur.org> <87373ghaza.fsf@gnu.org> <87d12krp5l.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="089e08231960511c93056291222b" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:32786) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eZvvX-0001ky-Dz for bug-guix@gnu.org; Fri, 12 Jan 2018 04:47:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eZvvS-0001nL-Ga for bug-guix@gnu.org; Fri, 12 Jan 2018 04:47:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:44981) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eZvvS-0001nE-DY for bug-guix@gnu.org; Fri, 12 Jan 2018 04:47:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87d12krp5l.fsf@gmail.com> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Alex Kost Cc: 29992@debbugs.gnu.org, =?UTF-8?Q?Cl=C3=A9ment?= Lassieur --089e08231960511c93056291222b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 2018-01-08 22:55 GMT+01:00 Alex Kost : > Ludovic Court=C3=A8s (2018-01-08 11:59 +0100) wrote: > > > Perhaps the proper way to stop postgresql is via one of its client > > commands, like we do for nginx? > > Regarding the commands: "pg_ctl" is the canonical tool to start/stop > PostgreSQL server. > > Note: I don't use the Guix service for postgresql (instead I run > postgres via my Shepherd user instance). > > -- > Alex > I'm sorry if this isn't the place to write about this My Tryton service doesn't get stopped either Here's a picture I took from a virtual machine https://imgur.com/a/LJ2Cq When I run Tryton myself, I use this line: trytond -c trytond.conf this command doesn' t return a prompt So, in order to stop Tryton I simply press Ctrl-C In the definition of my sevice, I use #~(make-kill-destructor) to stop the Tryton service But I copied this from other services, I don't know what "make-kill-destructor" does My Trytond service is not working anyway, I launch a vm with my service running in it, I test it with the client, I see it doesn't work, I stop it and then I'd like to launch it by hand to see something more But then, because a tryton-real daemon is still running, the socket for that address is already bound, as you can see in the picture Of course this has nothing to do with the Postgresql not stopping bug, I was only giving some context --089e08231960511c93056291222b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
2018-01-08 22:55 GMT+01:00 Alex Kost <= ;alezost@gmail.com>:
Ludovic Court=C3=A8s (2018-01-= 08 11:59 +0100) wrote:

> Perhaps the proper way to stop postgresql is via one of its client
> commands, like we do for nginx?

Regarding the commands: "pg_ctl" is the canonical tool to = start/stop
PostgreSQL server.

Note: I don't use the Guix service for postgresql (instead I run
postgres via my Shepherd user instance).

--
Alex

I'm sorry if thi= s isn't the place to write about this

My Tryton service doesn't get stopped either
Here's a picture I took from a virtua= l machine
https://imgur.com/a/LJ2C= q

When I run Tryton myself, I u= se this line:
trytond -c trytond.conf
this command doesn' t return a p= rompt
So, in order to stop Tryton I sim= ply press Ctrl-C

In the definition = of my sevice, I use
#~(make-kill-destructor)

to stop the Tryton service

But I copied this from other services, I don't know what "mak= e-kill-destructor" does

My Try= tond service is not working anyway, I launch a vm with my service running i= n it, I test=C2=A0 it with the client, I see it doesn't work, I stop it= and then I'd like to launch it by hand to see something more

But then, because a tryton-real daemon is st= ill running, the socket for that address is already bound, as you can see i= n the picture

Of course this has no= thing to do with the Postgresql not stopping bug, I was only giving some co= ntext
--089e08231960511c93056291222b--