From owner-freebsd-ports@FreeBSD.ORG Sat Jan 13 23:19:43 2007 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 305B516A40F for ; Sat, 13 Jan 2007 23:19:43 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.249]) by mx1.freebsd.org (Postfix) with ESMTP id 0A5A013C428 for ; Sat, 13 Jan 2007 23:19:42 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from [192.168.2.102] (adsl-65-69-140-8.dsl.rcsntx.swbell.net [65.69.140.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTP id BA275114307 for ; Sat, 13 Jan 2007 17:14:04 -0600 (CST) Date: Sat, 13 Jan 2007 17:19:41 -0600 From: Paul Schmehl To: FreeBSD Ports Message-ID: In-Reply-To: References: X-Mailer: Mulberry/4.0.7b1 (Mac OS X) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========7833E94BE41DC3DA86CA==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: Problems with pid files 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: Sat, 13 Jan 2007 23:19:43 -0000 --==========7833E94BE41DC3DA86CA========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On January 13, 2007 4:50:04 PM -0600 Paul Schmehl =20 wrote: > I just discovered a problem with two ports that I maintain, and I need > help figuring out how to fix it. The ports in question are > security/sguil-sensor and security/sguil-server. The problem, which I > just discovered today, is that, if both ports are installed on the same > machine (not the normal configuration), they create a pidfile with the > exact same name. Therefore, only one of the two ports will run at any > given time. > > I don't understand why this is happening. The sguil-sensor port uses an > init file named "sensor-agent.sh" and the sguil-server port uses an init > file named "sguild.sh". Both init scripts have the following in them: > check_process=3D"${command} /bin/sh". Both ports require special stop > routines to get them to stop properly. > This should have been check_process=3D"${procname} /bin/sh". > Both processes create a pid named sguild.pid. This is incorrect. The sguil-server port creates sguild.pid, and the=20 sguil-sensor port creates sensor-agent.pid. However, I'm still having the problem of the second process's startup=20 failing because it thinks the pid already exists. (Doesn't matter which=20 process you start first.) Any hints would be appreciated. Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========7833E94BE41DC3DA86CA==========--