From owner-freebsd-python@FreeBSD.ORG Sun Feb 22 01:28:45 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA8C916A4CE; Sun, 22 Feb 2004 01:28:45 -0800 (PST) Received: from postman.arcor.de (postman2.arcor-online.net [151.189.0.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20C2143D1D; Sun, 22 Feb 2004 01:28:45 -0800 (PST) (envelope-from eikemeier@fillmore-labs.com) Received: from fillmore.dyndns.org (port-212-202-51-138.reverse.qsc.de [212.202.51.138]) (authenticated bits=0)i1M9Scf5019247 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 22 Feb 2004 10:28:39 +0100 (MET) Received: from [172.16.0.2] (helo=fillmore-labs.com) by fillmore.dyndns.org with esmtp (Exim 4.30; FreeBSD) id 1Aupue-0009Xz-Bf; Sun, 22 Feb 2004 10:28:36 +0100 Message-ID: <40387643.9040805@fillmore-labs.com> Date: Sun, 22 Feb 2004 10:28:35 +0100 From: Oliver Eikemeier Organization: Fillmore Labs GmbH - http://www.fillmore-labs.com/ MIME-Version: 1.0 To: Hye-Shik Chang , Khairil Yusof Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit User-Agent: KMail/1.5.9 cc: FreeBSD Python Subject: USE_ZOPE vs. python modules X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Feb 2004 09:28:45 -0000 Dear maintainers, the breakage of www/zope-cmfphoto http://bento.freebsd.org/errorlogs/i386-4-full/zope-cmfphoto-0.4.r2.log seems to have roots in the current bsd.python.mk structure. Basically if you define USE_ZOPE in a port, you'll get Python 2.1 by default, if you just define USE_PYTHON You'll get Python 2.3. The result is that if a port that uses zope depends on an another that doesn't, you'll get different versions of the python modules (py21-imaging vs. py23-imaging in this case), which breaks installation. The workaround would be either to set the system-wide default to 2.1 or update zope to a version supporting 2.3. I am aware of the recent thread `Zope 2.6.4 vs 2.7', I just wanted to notify you because www/zope-cmfphoto is marked as BROKEN (and scheduled for removal), for reasons that lie beyond the responsibilites of this port (or its maintainer). Regards Oliver From owner-freebsd-python@FreeBSD.ORG Mon Feb 23 06:18:01 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DDE116A4CE for ; Mon, 23 Feb 2004 06:18:01 -0800 (PST) Received: from gioria.dyndns.org (dyn-83-154-125-9.ppp.tiscali.fr [83.154.125.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F3D643D2D for ; Mon, 23 Feb 2004 06:18:00 -0800 (PST) (envelope-from eagle@gioria.dyndns.org) Received: by gioria.dyndns.org (Postfix, from userid 501) id E9311374B9; Mon, 23 Feb 2004 15:40:04 +0100 (CET) Date: Mon, 23 Feb 2004 15:40:04 +0100 From: Sebastien Gioria To: python@FreeBSD.ORG Message-ID: <20040223154004.A9981@thorm.gioria.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Hostname: thorm.gioria.dyndns.org X-Uptime: 3:38PM up 19 days, 2:35, 3 users, load averages: 1.02, 1.05, 1.07 X-FreeBSD-Release: FreeBSD-4.7-STABLE Subject: Zope/plone X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Sebastien Gioria List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2004 14:18:01 -0000 Hi guys, Im' searching some links to best tune my FreeBSD systems for python/zope/plone optimization. The servers will do some shared hosting of zope server Thanks ! -- Sebastien Gioria(48.8147,2.3622) gioria@{FreeBSD,FreeBSD-FR}.ORG French FreeBSD User Group http://www.FreeBSD-FR.{ORG,info} FreeBSD committer http://www.FreeBSD.ORG *-> FreeBSD + RollerBlade + Scuba Diving; What need you more ? <-* From owner-freebsd-python@FreeBSD.ORG Mon Feb 23 07:28:47 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E16D616A4CE for ; Mon, 23 Feb 2004 07:28:47 -0800 (PST) Received: from miffy.openlook.org (openlook.org [211.236.182.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC0A643D1F for ; Mon, 23 Feb 2004 07:28:47 -0800 (PST) (envelope-from perky@miffy.openlook.org) Received: by miffy.openlook.org (Postfix, from userid 1000) id 029EFA9C2; Tue, 24 Feb 2004 00:32:19 +0900 (KST) Date: Tue, 24 Feb 2004 00:32:19 +0900 From: Hye-Shik Chang To: Oliver Eikemeier Message-ID: <20040223153219.GA92513@i18n.org> References: <40387643.9040805@fillmore-labs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40387643.9040805@fillmore-labs.com> X-Accept-Language: ko, en User-Agent: Mutt/1.5.5.1i cc: FreeBSD Python cc: Khairil Yusof Subject: Re: USE_ZOPE vs. python modules X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2004 15:28:48 -0000 On Sun, Feb 22, 2004 at 10:28:35AM +0100, Oliver Eikemeier wrote: > Dear maintainers, > > the breakage of www/zope-cmfphoto > http://bento.freebsd.org/errorlogs/i386-4-full/zope-cmfphoto-0.4.r2.log > seems to have roots in the current bsd.python.mk structure. > > Basically if you define USE_ZOPE in a port, you'll get Python 2.1 by > default, > if you just define USE_PYTHON You'll get Python 2.3. > > The result is that if a port that uses zope depends on an another that > doesn't, > you'll get different versions of the python modules (py21-imaging vs. > py23-imaging > in this case), which breaks installation. Correct. > The workaround would be either to set the system-wide default to 2.1 or > update > zope to a version supporting 2.3. I am aware of the recent thread `Zope > 2.6.4 vs 2.7', > I just wanted to notify you because www/zope-cmfphoto is marked as BROKEN > (and > scheduled for removal), for reasons that lie beyond the responsibilites of > this > port (or its maintainer). I'd like to see updating www/zope to 2.7 as soon as possible. I heard that 2.7 has enough backward-compatibility and we can avoid the problem then. Because current port infrastructure doesn't allow multiple installations from a same origin, we'll need to introduce "instance" concept for pkgdb. eg. this line on Makefile PYTHON_INSTALL_PERVERSION= yes applies bsd.python.mk .ifdef PYTHON_PERVERSION_INSTALLATION PKGINSTANCE= ${PYTHON_VERSION} .endif then check-already-installed target of bsd.pkg.mk checks @comment INSTANCE:python2.3 and if current port has different instance string, allows further installation phases. This is still a rough sketch. And I think "instance" concept will be useful for apache/perl/ruby ports, too. What do you think on this? Regards, Hye-Shik From owner-freebsd-python@FreeBSD.ORG Mon Feb 23 07:49:01 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9824116A4CE for ; Mon, 23 Feb 2004 07:49:01 -0800 (PST) Received: from postman.arcor.de (postman2.arcor-online.net [151.189.0.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F47443D2D for ; Mon, 23 Feb 2004 07:49:01 -0800 (PST) (envelope-from eikemeier@fillmore-labs.com) Received: from fillmore.dyndns.org (port-212-202-51-138.reverse.qsc.de [212.202.51.138]) (authenticated bits=0)i1NFmwf5008158 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 23 Feb 2004 16:48:58 +0100 (MET) Received: from [172.16.0.2] (helo=fillmore-labs.com) by fillmore.dyndns.org with esmtp (Exim 4.30; FreeBSD) id 1AvIKF-000FYD-Sa; Mon, 23 Feb 2004 16:48:55 +0100 Message-ID: <403A20E7.8080506@fillmore-labs.com> Date: Mon, 23 Feb 2004 16:48:55 +0100 From: Oliver Eikemeier Organization: Fillmore Labs GmbH - http://www.fillmore-labs.com/ MIME-Version: 1.0 To: Hye-Shik Chang References: <40387643.9040805@fillmore-labs.com> <20040223153219.GA92513@i18n.org> In-Reply-To: <20040223153219.GA92513@i18n.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit User-Agent: KMail/1.5.9 cc: FreeBSD Python cc: Khairil Yusof Subject: Re: USE_ZOPE vs. python modules X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2004 15:49:01 -0000 Hye-Shik Chang wrote: > On Sun, Feb 22, 2004 at 10:28:35AM +0100, Oliver Eikemeier wrote: > > [...] > > I'd like to see updating www/zope to 2.7 as soon as possible. I > heard that 2.7 has enough backward-compatibility and we can avoid > the problem then. Because current port infrastructure doesn't allow > multiple installations from a same origin, we'll need to introduce > "instance" concept for pkgdb. eg. > > this line on Makefile > > PYTHON_INSTALL_PERVERSION= yes You don't want to have a variable named like that ;) > applies bsd.python.mk > > .ifdef PYTHON_PERVERSION_INSTALLATION > PKGINSTANCE= ${PYTHON_VERSION} > .endif > > then check-already-installed target of bsd.pkg.mk checks > @comment INSTANCE:python2.3 > and if current port has different instance string, allows further > installation phases. > > This is still a rough sketch. And I think "instance" concept will > be useful for apache/perl/ruby ports, too. What do you think on > this? It looks like you need extensive patches for this, especially to the pkg_install in the base system, so this solution won't happen soon and is not backwards compatible to older systems. Apache and perl ports normally conflicts, so there can be only one, and you can solve it by requiring the port you want to live with. The point is that defaults should not change, depending on other options that can change during the build. Defaulting to different perl versions depending on OSREL is ok, since this doesn't change. Defaulting to different python versions depending on USE_ZOPE is problematic. Regards Oliver From owner-freebsd-python@FreeBSD.ORG Mon Feb 23 15:32:11 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2B9B16A4CE for ; Mon, 23 Feb 2004 15:32:11 -0800 (PST) Received: from smtp013.mail.yahoo.com (smtp013.mail.yahoo.com [216.136.173.57]) by mx1.FreeBSD.org (Postfix) with SMTP id 9381243D2D for ; Mon, 23 Feb 2004 15:32:11 -0800 (PST) (envelope-from kaeru@pd.jaring.my) Received: from unknown (HELO ?219.95.57.68?) (khairil?yusof@219.95.57.68 with plain) by smtp013.mail.yahoo.com with SMTP; 23 Feb 2004 23:32:10 -0000 From: Khairil Yusof To: Sebastien Gioria In-Reply-To: <20040223154004.A9981@thorm.gioria.dyndns.org> References: <20040223154004.A9981@thorm.gioria.dyndns.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-5eVG0qbp4oltRZAmt9xM" Message-Id: <1077579123.7414.99.camel@wolverine.cerebro.net.my> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.5.4FreeBSD GNOME Team Port Date: Tue, 24 Feb 2004 07:32:04 +0800 cc: python@FreeBSD.ORG Subject: Re: Zope/plone X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2004 23:32:11 -0000 --=-5eVG0qbp4oltRZAmt9xM Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2004-02-23 at 15:40 +0100, Sebastien Gioria wrote: > I'm searching some links to best tune my FreeBSD systems > for python/zope/plone optimization. George Donnelly would know more about this. ;)=20 Right now I don't think there are FreeBSD specific links. FreeBSD specific, until Zope 2.7 and Plone 2.0 make it into the ports, it's better to install them from source. Both versions in the ports, are deprecated, and Zope 2.6 is using an old version of python (2.1) which is generally slower. If you have an SMP machine, run multiple ZOE clients per machine to match the CPU number. The main speed improvements are not FreeBSD specific. Namely using apache/squid as a front end http accelerator (cache) and using ZOE to cluster your servers. -- "You keep using that word. I do not think it means what you think it means." FreeBSD 5.2-CURRENT i386 7:09am up 2 days, 4:21, 3 users, load averages: 2.67, 1.65, 1.14 --=-5eVG0qbp4oltRZAmt9xM Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAOo1zDAqnLW/+/X8RAo3wAKDkrRaV7BU6qpR4/oAtmfCSFlCLTwCg4ros A0ZSlbVDQZiWZ7KW0+CBOLA= =2/A9 -----END PGP SIGNATURE----- --=-5eVG0qbp4oltRZAmt9xM-- From owner-freebsd-python@FreeBSD.ORG Mon Feb 23 17:16:29 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5FC016A4CE; Mon, 23 Feb 2004 17:16:29 -0800 (PST) Received: from diligence.flag.rootnode.com (adsl-65-67-81-98.dsl.ltrkar.swbell.net [65.67.81.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9E1543D1F; Mon, 23 Feb 2004 17:16:29 -0800 (PST) (envelope-from joe@osoft.us) Received: from osoft.us (coherence.flag.rootnode.com [10.0.1.105]) by diligence.flag.rootnode.com (Postfix) with ESMTP id ED7A5D4AA; Mon, 23 Feb 2004 19:16:28 -0600 (CST) Message-ID: <403AA655.8000801@osoft.us> Date: Mon, 23 Feb 2004 19:18:13 -0600 From: Joe Koberg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sebastien Gioria References: <20040223154004.A9981@thorm.gioria.dyndns.org> In-Reply-To: <20040223154004.A9981@thorm.gioria.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: python@FreeBSD.ORG Subject: Re: Zope/plone X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 01:16:30 -0000 Sebastien Gioria wrote: >Im' searching some links to best tune my FreeBSD systems >for python/zope/plone optimization. > >The servers will do some shared hosting of zope server > > > Make python from ports and set WANT_HUGE_STACK_SIZE: /usr/ports/lang/python $ make WANT_HUGE_STACK_SIZE=yes ... This sets a 1MB instead of 128KB stack size for threads in python. Plone in particluar needs this to prevent core dumps, but I have only seen it happen under python 2.1 and zope <=2.6. FreeBSD 4.6 - 4.8. I say install zope/plone from plain source, not ports. If you have an SMP system and are looking for production speed under load, I hear you should run a ZEO storage server process and run a client Zope instance for each processor. Then load-balance incoming requests onto all those with Apache or other magic. I don't know how sessions work with this setup. It also reduces impact of the python global interpreter lock (only one thread can enter the python interpreter at a time). Running a ZEO server is supposed to be good for other reasons too. You better have a lot of memory though. Joe Koberg joe x osoft.us Python, Zope, and Plone consultants Little Rock AR http://osoft.us/ From owner-freebsd-python@FreeBSD.ORG Tue Feb 24 01:14:52 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF11816A4CE for ; Tue, 24 Feb 2004 01:14:52 -0800 (PST) Received: from miffy.openlook.org (openlook.org [211.236.182.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F8DF43D31 for ; Tue, 24 Feb 2004 01:14:52 -0800 (PST) (envelope-from perky@miffy.openlook.org) Received: by miffy.openlook.org (Postfix, from userid 1000) id 86651A9C8; Tue, 24 Feb 2004 18:18:27 +0900 (KST) Date: Tue, 24 Feb 2004 18:18:27 +0900 From: Hye-Shik Chang To: Jeremy Messenger Message-ID: <20040224091827.GA9742@i18n.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Accept-Language: ko, en User-Agent: Mutt/1.5.5.1i cc: python@FreeBSD.org Subject: Re: Need the help on debug the Python VS libpthread.. X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 09:14:52 -0000 On Fri, Feb 20, 2004 at 01:36:03AM +0000, Jeremy Messenger wrote: > Hello, > > net/straw will fail install if it's on libpthread, but it doesn't fail on > libc_r.. I have no idea where the problem is yet, but would be nice if > anyone with the skill debugger can help. The problem is in this log > http://bento.freebsd.org/errorlogs/i386-5-latest/straw-0.22.log .. > > ============================= > [...] > byte-compiling /usr/X11R6/share/gnome/straw/URLFetch.py to URLFetch.pyc > byte-compiling /usr/X11R6/share/gnome/straw/utils.py to utils.pyc > writing byte-compilation script '/tmp/tmpXHlc42.py' > /usr/local/bin/python -O /tmp/tmpXHlc42.py > error: Interrupted system call > *** Error code 1 > ============================= A workaround is got into python port 2.3.3_2. Please test it whether it works. :) > I am not sure if it's Python problem, it might be one of net/straw's > dependencies. I am not sure if it's Python problem or our libpthread problem. I failed to reproduce the situation with compact C code. (waitpid(2) returned -1 with errno=EINTR on a child's normal termination.) If you get a reasonable explanation that saying it's Python's problem, please tell me. Hye-Shik From owner-freebsd-python@FreeBSD.ORG Tue Feb 24 01:38:46 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59BE716A4CF for ; Tue, 24 Feb 2004 01:38:46 -0800 (PST) Received: from smtp102.mail.sc5.yahoo.com (smtp102.mail.sc5.yahoo.com [216.136.174.140]) by mx1.FreeBSD.org (Postfix) with SMTP id 8772443D45 for ; Tue, 24 Feb 2004 01:38:45 -0800 (PST) (envelope-from kaeru@pd.jaring.my) Received: from unknown (HELO ?219.95.58.193?) (khairil?yusof@219.95.58.193 with plain) by smtp102.mail.sc5.yahoo.com with SMTP; 24 Feb 2004 09:38:44 -0000 From: Khairil Yusof To: Hye-Shik Chang In-Reply-To: <20040224091827.GA9742@i18n.org> References: <20040224091827.GA9742@i18n.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-yXcF1vPKpc7gxCe3petF" Message-Id: <1077615520.1002.10.camel@wolverine.cerebro.net.my> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.5.4FreeBSD GNOME Team Port Date: Tue, 24 Feb 2004 17:38:41 +0800 cc: Jeremy Messenger cc: python@FreeBSD.org Subject: Re: Need the help on debug the Python VS libpthread.. X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 09:38:46 -0000 --=-yXcF1vPKpc7gxCe3petF Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2004-02-24 at 18:18 +0900, Hye-Shik Chang wrote: > I am not sure if it's Python problem or our libpthread problem. I > failed to reproduce the situation with compact C code. (waitpid(2) > returned -1 with errno=3DEINTR on a child's normal termination.) > If you get a reasonable explanation that saying it's Python's > problem, please tell me. Great, thanks for the info. I can duplicate this problem with mail/ evolution also. It may be a more universal problem caused by libpthread. At least it also effects evolution1.5's em-junk-filter.c and other shell calls that use waitpid. evolution doesn't catch it either, resulting in a hanged process loop that has to be killed (also under libpthread). -- "You keep using that word. I do not think it means what you think it means." FreeBSD 5.2-CURRENT i386 5:26pm up 1:05, 1 user, load averages: 0.58, 0.40, 0.42 --=-yXcF1vPKpc7gxCe3petF Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAOxugDAqnLW/+/X8RAhOJAKD3gFuYXFSDmKiv2tUJdRGxvzrYUACg72vQ v1WwHdGUypY5D2ZeiLiLzyk= =O2NB -----END PGP SIGNATURE----- --=-yXcF1vPKpc7gxCe3petF-- From owner-freebsd-python@FreeBSD.ORG Tue Feb 24 08:27:50 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55CF116A4CE; Tue, 24 Feb 2004 08:27:50 -0800 (PST) Received: from lakemtao06.cox.net (lakemtao06.cox.net [68.1.17.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2F8F43D1D; Tue, 24 Feb 2004 08:27:49 -0800 (PST) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.11]) by lakemtao06.cox.net (InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with ESMTP id <20040224162749.PISN3458.lakemtao06.cox.net@mezz.mezzweb.com>; Tue, 24 Feb 2004 11:27:49 -0500 Date: Tue, 24 Feb 2004 10:26:42 -0600 To: Khairil Yusof References: <20040224091827.GA9742@i18n.org> <1077615520.1002.10.camel@wolverine.cerebro.net.my> From: Jeremy Messenger Content-Type: text/plain; format=flowed; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <1077615520.1002.10.camel@wolverine.cerebro.net.my> User-Agent: Opera7.23/Linux M2 build 518 cc: freebsd-threads@freebsd.org cc: python@FreeBSD.org cc: Hye-Shik Chang Subject: Re: Need the help on debug the Python VS libpthread.. X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 16:27:50 -0000 Great, thank guys! I now can install net/straw with optimized on libpthread. I am adding -thread in the CC, so the thread developers can catch here too. :-) Cheers, Mezz On Tue, 24 Feb 2004 17:38:41 +0800, Khairil Yusof wrote: > On Tue, 2004-02-24 at 18:18 +0900, Hye-Shik Chang wrote: > >> I am not sure if it's Python problem or our libpthread problem. I >> failed to reproduce the situation with compact C code. (waitpid(2) >> returned -1 with errno=EINTR on a child's normal termination.) >> If you get a reasonable explanation that saying it's Python's >> problem, please tell me. > > Great, thanks for the info. I can duplicate this problem with mail/ > evolution also. > > It may be a more universal problem caused by libpthread. At least it > also effects evolution1.5's em-junk-filter.c and other shell calls that > use waitpid. evolution doesn't catch it either, resulting in a hanged > process loop that has to be killed (also under libpthread). > > -- > "You keep using that word. I do not think it means what you think it > means." > > FreeBSD 5.2-CURRENT i386 > 5:26pm up 1:05, 1 user, load averages: 0.58, 0.40, 0.42 -- bsdforums.org 's moderator, mezz. From owner-freebsd-python@FreeBSD.ORG Tue Feb 24 10:57:36 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E374616A4CE; Tue, 24 Feb 2004 10:57:36 -0800 (PST) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD69443D31; Tue, 24 Feb 2004 10:57:34 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc13) with ESMTP id <2004022418573301500l3g4le>; Tue, 24 Feb 2004 18:57:34 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA78365; Tue, 24 Feb 2004 10:57:33 -0800 (PST) Date: Tue, 24 Feb 2004 10:57:32 -0800 (PST) From: Julian Elischer To: Jeremy Messenger In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Hye-Shik Chang cc: python@FreeBSD.org cc: Khairil Yusof cc: freebsd-threads@freebsd.org Subject: Re: Need the help on debug the Python VS libpthread.. X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 18:57:37 -0000 On Tue, 24 Feb 2004, Jeremy Messenger wrote: > Great, thank guys! I now can install net/straw with optimized on > libpthread. I am adding -thread in the CC, so the thread developers can > catch here too. :-) so what was fixed between teh quoted mail below and now? > > Cheers, > Mezz > > On Tue, 24 Feb 2004 17:38:41 +0800, Khairil Yusof > wrote: > > > On Tue, 2004-02-24 at 18:18 +0900, Hye-Shik Chang wrote: > > > >> I am not sure if it's Python problem or our libpthread problem. I > >> failed to reproduce the situation with compact C code. (waitpid(2) > >> returned -1 with errno=EINTR on a child's normal termination.) > >> If you get a reasonable explanation that saying it's Python's > >> problem, please tell me. > > > > Great, thanks for the info. I can duplicate this problem with mail/ > > evolution also. > > > > It may be a more universal problem caused by libpthread. At least it > > also effects evolution1.5's em-junk-filter.c and other shell calls that > > use waitpid. evolution doesn't catch it either, resulting in a hanged > > process loop that has to be killed (also under libpthread). > > > > -- > > "You keep using that word. I do not think it means what you think it > > means." > > > > FreeBSD 5.2-CURRENT i386 > > 5:26pm up 1:05, 1 user, load averages: 0.58, 0.40, 0.42 > > > -- > bsdforums.org 's moderator, mezz. > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" > From owner-freebsd-python@FreeBSD.ORG Tue Feb 24 11:50:12 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47A1416A4CE; Tue, 24 Feb 2004 11:50:12 -0800 (PST) Received: from lakemtao06.cox.net (lakemtao06.cox.net [68.1.17.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id A673F43D39; Tue, 24 Feb 2004 11:50:11 -0800 (PST) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.11]) by lakemtao06.cox.net (InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with ESMTP id <20040224195011.SUDZ3458.lakemtao06.cox.net@mezz.mezzweb.com>; Tue, 24 Feb 2004 14:50:11 -0500 Date: Tue, 24 Feb 2004 13:49:05 -0600 To: Julian Elischer References: From: Jeremy Messenger Content-Type: text/plain; format=flowed; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: User-Agent: Opera7.23/Linux M2 build 518 cc: Hye-Shik Chang cc: python@FreeBSD.org cc: Khairil Yusof cc: freebsd-threads@freebsd.org Subject: Re: Need the help on debug the Python VS libpthread.. X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 19:50:12 -0000 On Tue, 24 Feb 2004 10:57:32 -0800 (PST), Julian Elischer wrote: > > > On Tue, 24 Feb 2004, Jeremy Messenger wrote: > >> Great, thank guys! I now can install net/straw with optimized on >> libpthread. I am adding -thread in the CC, so the thread developers can >> catch here too. :-) > > so what was fixed between teh quoted mail below and now? A workaround (not real fix?) as perky has committed[1]. There's something wrong with waitpid if it runs as libpthread, since without the workaround can run fine with libc_r. [1] http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/python/files/patch-Lib%3a%3adistutils%3a%3aspawn.py Cheers, Mezz >> Cheers, >> Mezz >> >> On Tue, 24 Feb 2004 17:38:41 +0800, Khairil Yusof >> wrote: >> >> > On Tue, 2004-02-24 at 18:18 +0900, Hye-Shik Chang wrote: >> > >> >> I am not sure if it's Python problem or our libpthread problem. I >> >> failed to reproduce the situation with compact C code. (waitpid(2) >> >> returned -1 with errno=EINTR on a child's normal termination.) >> >> If you get a reasonable explanation that saying it's Python's >> >> problem, please tell me. >> > >> > Great, thanks for the info. I can duplicate this problem with mail/ >> > evolution also. >> > >> > It may be a more universal problem caused by libpthread. At least it >> > also effects evolution1.5's em-junk-filter.c and other shell calls >> that >> > use waitpid. evolution doesn't catch it either, resulting in a hanged >> > process loop that has to be killed (also under libpthread). >> > >> > -- >> > "You keep using that word. I do not think it means what you think it >> > means." >> > >> > FreeBSD 5.2-CURRENT i386 >> > 5:26pm up 1:05, 1 user, load averages: 0.58, 0.40, 0.42 -- bsdforums.org 's moderator, mezz. From owner-freebsd-python@FreeBSD.ORG Tue Feb 24 14:26:24 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4927916A4CE; Tue, 24 Feb 2004 14:26:24 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF08743D2F; Tue, 24 Feb 2004 14:26:23 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i1OMQDDF005092; Tue, 24 Feb 2004 17:26:13 -0500 (EST) Date: Tue, 24 Feb 2004 17:26:13 -0500 (EST) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Jeremy Messenger In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-threads@freebsd.org cc: python@freebsd.org cc: Julian Elischer cc: Hye-Shik Chang Subject: Re: Need the help on debug the Python VS libpthread.. X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 22:26:24 -0000 On Tue, 24 Feb 2004, Jeremy Messenger wrote: > On Tue, 24 Feb 2004 10:57:32 -0800 (PST), Julian Elischer > wrote: > > > > > > > On Tue, 24 Feb 2004, Jeremy Messenger wrote: > > > >> Great, thank guys! I now can install net/straw with optimized on > >> libpthread. I am adding -thread in the CC, so the thread developers can > >> catch here too. :-) > > > > so what was fixed between teh quoted mail below and now? > > A workaround (not real fix?) as perky has committed[1]. There's something > wrong with waitpid if it runs as libpthread, since without the workaround > can run fine with libc_r. It is not necessarily a problem with libpthread. waitpid() can return EINTR when interrupted by a signal. If SIGCHLD isn't masked by the thread, then it is certainly plausible that it can get interrupted by it. You may not have seen it with libc_r because it handles signals differently as well as wrap waitpid() so it doesn't block the process. Libpthread doesn't wrap waitpid() except to make it a cancellation point. If its returning EINTR, I would suspect that it has received a signal. -- Dan Eischen From owner-freebsd-python@FreeBSD.ORG Tue Feb 24 16:42:47 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 718E316A4CE for ; Tue, 24 Feb 2004 16:42:47 -0800 (PST) Received: from miffy.openlook.org (openlook.org [211.236.182.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 037AF43D1D for ; Tue, 24 Feb 2004 16:42:47 -0800 (PST) (envelope-from perky@miffy.openlook.org) Received: by miffy.openlook.org (Postfix, from userid 1000) id A915DA9C1; Wed, 25 Feb 2004 09:46:25 +0900 (KST) Date: Wed, 25 Feb 2004 09:46:25 +0900 From: Hye-Shik Chang To: Daniel Eischen Message-ID: <20040225004625.GA20828@i18n.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Accept-Language: ko, en User-Agent: Mutt/1.5.5.1i cc: Jeremy Messenger cc: Julian Elischer cc: python@freebsd.org Subject: Re: Need the help on debug the Python VS libpthread.. X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2004 00:42:47 -0000 On Tue, Feb 24, 2004 at 05:26:13PM -0500, Daniel Eischen wrote: > On Tue, 24 Feb 2004, Jeremy Messenger wrote: > > > A workaround (not real fix?) as perky has committed[1]. There's something > > wrong with waitpid if it runs as libpthread, since without the workaround > > can run fine with libc_r. > > It is not necessarily a problem with libpthread. waitpid() can > return EINTR when interrupted by a signal. If SIGCHLD isn't > masked by the thread, then it is certainly plausible that it > can get interrupted by it. > > You may not have seen it with libc_r because it handles signals > differently as well as wrap waitpid() so it doesn't block the > process. Libpthread doesn't wrap waitpid() except to make it > a cancellation point. If its returning EINTR, I would suspect > that it has received a signal. I see. Thanks for the kind explanation and sorry for my confusing. :) The fix is checked in Python CVS. http://mail.python.org/pipermail/python-checkins/2004-February/039939.html Thanks, Hye-Shik From owner-freebsd-python@FreeBSD.ORG Tue Feb 24 17:05:21 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADC1616A4CE for ; Tue, 24 Feb 2004 17:05:21 -0800 (PST) Received: from miffy.openlook.org (openlook.org [211.236.182.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82E1E43D1D for ; Tue, 24 Feb 2004 17:05:21 -0800 (PST) (envelope-from perky@miffy.openlook.org) Received: by miffy.openlook.org (Postfix, from userid 1000) id AE365A950; Wed, 25 Feb 2004 10:09:00 +0900 (KST) Date: Wed, 25 Feb 2004 10:09:00 +0900 From: Hye-Shik Chang To: Oliver Eikemeier Message-ID: <20040225010900.GA21107@i18n.org> References: <40387643.9040805@fillmore-labs.com> <20040223153219.GA92513@i18n.org> <403A20E7.8080506@fillmore-labs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <403A20E7.8080506@fillmore-labs.com> X-Accept-Language: ko, en User-Agent: Mutt/1.5.5.1i cc: FreeBSD Python cc: Khairil Yusof Subject: Re: USE_ZOPE vs. python modules X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2004 01:05:21 -0000 On Mon, Feb 23, 2004 at 04:48:55PM +0100, Oliver Eikemeier wrote: > Hye-Shik Chang wrote: > > >On Sun, Feb 22, 2004 at 10:28:35AM +0100, Oliver Eikemeier wrote: [snip] > >then check-already-installed target of bsd.pkg.mk checks > >@comment INSTANCE:python2.3 > >and if current port has different instance string, allows further > >installation phases. > > > >This is still a rough sketch. And I think "instance" concept will > >be useful for apache/perl/ruby ports, too. What do you think on > >this? > > It looks like you need extensive patches for this, especially to the > pkg_install in the base system, so this solution won't happen soon and > is not backwards compatible to older systems. > > Apache and perl ports normally conflicts, so there can be only one, and > you can solve it by requiring the port you want to live with. The point > is that defaults should not change, depending on other options that can > change during the build. Yes. That's a problem. But different to apache and perl ports, lang/python* ports are not mutually exclusive. They can live together peacefully if multiple instance installation from same origin is allowed and it's useful for compatibility tests. > Defaulting to different perl versions depending > on OSREL is ok, since this doesn't change. Defaulting to different python > versions depending on USE_ZOPE is problematic. > Historically saying, Zope tends to use undocumented features of Python and it makes that Zope to be very particular for python versions. Zope users may want to run their server extra-stable. And Zope used to recommend old version of Python for best fit for major portion of their life time. I think using different default python version is unavoidable though it's possible for now. Regards, Hye-Shik