Date: Sat, 13 Jan 2007 17:19:41 -0600 From: Paul Schmehl <pauls@utdallas.edu> To: FreeBSD Ports <ports@freebsd.org> Subject: Re: Problems with pid files Message-ID: <F53729C6CDBAFD4E8FC535DF@paul-schmehls-powerbook59.local> In-Reply-To: <EC06AC1114256AA8A0FD45B1@paul-schmehls-powerbook59.local> References: <EC06AC1114256AA8A0FD45B1@paul-schmehls-powerbook59.local>
next in thread | previous in thread | raw e-mail | index | archive | help
--==========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 <pauls@utdallas.edu>=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==========--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F53729C6CDBAFD4E8FC535DF>