Date: Thu, 21 Jul 2005 16:01:23 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: Paul Schmehl <pauls@utdallas.edu> Cc: freebsd-rc@freebsd.org Subject: Re: New port startup script fails Message-ID: <20050721230123.GA19090@odin.ac.hmc.edu> In-Reply-To: <468B58E789145A1C6885EA66@utd59514.utdallas.edu> References: <468B58E789145A1C6885EA66@utd59514.utdallas.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 21, 2005 at 05:50:12PM -0500, Paul Schmehl wrote: > I'm working on a new port, and I decided to use the new rc.subr type=20 > startup script. After I wrote the script, I started testing it. The=20 > program started fine, but neither stop nor status worked. I read man (8)= =20 > rc.subr and studied the script (/etc/rc.subr). >=20 > The program was creating a pid file with the correct name in /var/run, bu= t=20 > for some reason, the stop and status commands apparently couldn't find?= =20 > read? the file. Is there a way to troubleshoot this problem to pin down= =20 > exactly were the problem is? Far too many things could be wrong for us to do more than speculate. Please send the script in question. A couple of ideas. First, are you setting the pidfile variable? If not, you may need to. Second, does the program in question change it's name? If so, you may have to implement stop and status by hand. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFC4ClCXY6L6fI4GtQRApjdAJ435s7AOaHNW9N9FkWgHln1TUShdwCdFHI6 6wQ17Bb7lstgl3Tn3IBM6TI= =ZzbY -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050721230123.GA19090>