From owner-freebsd-python@FreeBSD.ORG  Sat Sep  7 12:15:09 2013
Return-Path: <owner-freebsd-python@FreeBSD.ORG>
Delivered-To: freebsd-python@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 4FE53A31
 for <freebsd-python@freebsd.org>; Sat,  7 Sep 2013 12:15:09 +0000 (UTC)
 (envelope-from mva@FreeBSD.org)
Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de
 [80.67.31.38])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0C77B2D6A
 for <freebsd-python@freebsd.org>; Sat,  7 Sep 2013 12:15:09 +0000 (UTC)
Received: from [89.183.9.2] (helo=localhost)
 by smtprelay04.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256)
 (Exim 4.68) (envelope-from <mva@FreeBSD.org>) id 1VIHPL-0001NC-U8
 for freebsd-python@freebsd.org; Sat, 07 Sep 2013 14:14:32 +0200
Date: Sat, 7 Sep 2013 14:14:31 +0200
From: Marcus von Appen <mva@FreeBSD.org>
To: freebsd-python@freebsd.org
Subject: Re: Python and SIGINT, SIGTERM.
Message-ID: <20130907121431.GA1301@medusa.sysfault.org>
Mail-Followup-To: freebsd-python@freebsd.org
References: <CAJuc1zNzDRx+F13SKoDwYezWCUSZ7-GW3M6mDkR43u4ycK9_=g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="UlVJffcvxoiEqYs2"
Content-Disposition: inline
In-Reply-To: <CAJuc1zNzDRx+F13SKoDwYezWCUSZ7-GW3M6mDkR43u4ycK9_=g@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Df-Sender: MTEyNTc0Mg==
X-BeenThere: freebsd-python@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: Marcus von Appen <mva@FreeBSD.org>
List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-python>,
 <mailto:freebsd-python-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python>
List-Post: <mailto:freebsd-python@freebsd.org>
List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>,
 <mailto:freebsd-python-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Sep 2013 12:15:09 -0000


--UlVJffcvxoiEqYs2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On, Mon Aug 26, 2013, Jonathan Chen wrote:

> Hi,
>
> I'm currently trying to use FreeBSD as my main python development O/S,
> and I'm noticing some oddness when I'm working with OpenERP. If I
> start the server from command line, a ^C to stop the server is rarely
> honoured. Similarly, when working with Eclipse + PyDev, a request to
> terminate a running instance will leave the process still actively
> running. In most cases, only a SIGKILL will work.
>
> I do not see this sort of behaviour when I'm using Ubuntu. Is this a
> problem with OpenERP, or does the problem lie with our python port?

Do you use the same version of OpenERP on both systems with the same
patches and build flags or a specific (probably prebuilt) build for each
of them?

If it is the latter case, can you ensure that OpenERP does not catch the
signals in order to shut down more gracefully?

Cheers
Marcus

--UlVJffcvxoiEqYs2
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (FreeBSD)

iEYEARECAAYFAlIrGKcACgkQi68/ErJnpkd7GgCgvL0+raFxNpw7UEJDVeky1xPT
mdkAoLulUNWOgOuFTXuT3pS3vTN5tiIq
=1Ds7
-----END PGP SIGNATURE-----

--UlVJffcvxoiEqYs2--