From owner-freebsd-ports@FreeBSD.ORG Thu Oct 28 17:14:18 2010 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97606106564A; Thu, 28 Oct 2010 17:14:18 +0000 (UTC) (envelope-from mike.jakubik@intertainservices.com) Received: from mail.intertainservices.com (mail.intertainservices.com [69.77.177.114]) by mx1.freebsd.org (Postfix) with ESMTP id 2C1F48FC20; Thu, 28 Oct 2010 17:14:18 +0000 (UTC) Received: from [172.16.10.166] (unknown [172.16.10.166]) by mail.intertainservices.com (Postfix) with ESMTPA id 222D156B9F; Thu, 28 Oct 2010 13:14:17 -0400 (EDT) From: Mike Jakubik To: Alex Dupre In-Reply-To: <4CC87287.6040607@FreeBSD.org> References: <1269425224.38906.6.camel@yan.home> <4BAB3B9F.9080100@FreeBSD.org> <1288203978.2052.2.camel@mjakubik-laptop> <4CC87287.6040607@FreeBSD.org> Date: Thu, 28 Oct 2010 13:14:16 -0400 Message-ID: <1288286056.7991.5.camel@mjakubik-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 X-intertainservices-MailScanner-Information: Please contact the ISP for more information X-intertainservices-MailScanner-ID: 222D156B9F.A075F X-intertainservices-MailScanner: Found to be clean X-intertainservices-MailScanner-From: mike.jakubik@intertainservices.com X-Spam-Status: No Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: ports@FreeBSD.org, yan@zlobin.name Subject: Re: FreeBSD Port: tomcat-6.0.24 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2010 17:14:18 -0000 On Wed, 2010-10-27 at 20:42 +0200, Alex Dupre wrote: > Mike Jakubik ha scritto: > > Does anyone have a working solution for this? The status command still > > does not work in tomcat 6.0.29. The above suggestion does not work either. > > The status command works on tomcat 6/7 ports. > Indeed it does, i reinstalled the port and it's working fine now, my startup script wasn't updated previously for some reason it seems. Thanks!