From owner-freebsd-python@FreeBSD.ORG Wed Jul 28 04:43:57 2010 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E8191065679 for ; Wed, 28 Jul 2010 04:43:57 +0000 (UTC) (envelope-from rrborg@speakeasy.net) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.39]) by mx1.freebsd.org (Postfix) with ESMTP id 6DFCF8FC19 for ; Wed, 28 Jul 2010 04:43:57 +0000 (UTC) Received: (qmail 27538 invoked from network); 28 Jul 2010 04:15:55 -0000 Received: from c-67-187-169-218.hsd1.ca.comcast.net (HELO [192.168.1.141]) (rrborg@[67.187.169.218]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 28 Jul 2010 04:15:55 -0000 Message-ID: <4C4FAF05.7060600@speakeasy.net> Date: Tue, 27 Jul 2010 21:16:05 -0700 From: Rocky Borg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6 MIME-Version: 1.0 To: freebsd-python@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: porting python script from linux to freebsd X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2010 04:43:57 -0000 I hope this is the right place to direct this question. I've been trying to track down a python issue that is specific to freebsd. The Cherokee webserver (http://www.freshports.org/www/cherokee/) has a python gui backend to admin the server. It works perfectly under Linux. Unfortunately it doesn't work correctly under FreeBSD. There aren't a lot of people that use FreeBSD to run cherokee so the main developers don't seem to interested in fixing it. I'm trying to track down the bug. If cherokee is started from rc.d scripts or command line it works fine. You can stop the server cleanly. But once it's started from the admin interface (which uses python) it can't be stopped. The admin interface shows that it sees cherokee running on the correct pid but once started from the admin interface the server can't be stopped (/usr/local/etc/rc.d/cherokee stop stops working also). Any information would be greatly appreciated since it's hard finding issues specific to freebsd/python. And the basic attitude seems to be if it works on linux that's good enough. Has anyone experienced this sort of problem on FreeBSD or perhaps could direct me to something that would explain what's going on. Bug report on the issue: http://code.google.com/p/cherokee/issues/detail?id=527 http://www.cherokee-project.com Script that handles starting and stopping the server: http://www.ctwow.net/sladeimages/Cherokee.py Any help would be greatly appreciated.