From owner-freebsd-questions@FreeBSD.ORG Tue Nov 25 06:08:34 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2752A16A4CF for ; Tue, 25 Nov 2003 06:08:34 -0800 (PST) Received: from mail.caraldi.com (caraldi.com [62.212.102.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3CA543FBD for ; Tue, 25 Nov 2003 06:08:32 -0800 (PST) (envelope-from jbq@caraldi.com) Received: from watt.intra.caraldi.com (watt.intra.caraldi.com [192.168.100.101]) by mail.caraldi.com (Postfix) with ESMTP id 0379820EC for ; Tue, 25 Nov 2003 15:08:31 +0100 (CET) Received: by watt.intra.caraldi.com (Postfix, from userid 1001) id C4FF2C6; Tue, 25 Nov 2003 15:08:31 +0100 (CET) Date: Tue, 25 Nov 2003 15:08:31 +0100 From: Jean-Baptiste Quenot To: freebsd-questions@freebsd.org Message-ID: <20031125140829.GD1256@watt.intra.caraldi.com> Mail-Followup-To: freebsd-questions@freebsd.org References: <20031124172222.GA20475@artax.karlin.mff.cuni.cz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zx4FCpZtqtKETZ7O" Content-Disposition: inline In-Reply-To: <20031124172222.GA20475@artax.karlin.mff.cuni.cz> User-Agent: Mutt/1.5.5.1i Subject: Re: stop_cmd=":" in pccard X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Nov 2003 14:08:34 -0000 --zx4FCpZtqtKETZ7O Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Jan Stary: > Why does /et/rc.d/pccard say stop_cmd=3D":"? This does, of course, not > 'stop' pccardd. After checking with several rc scripts, I noticed that stop_cmd is a null command for all the programs that don't have a well-defined pid file. Programs for which the pid file location is not predictable cannot be stopped by the rc mechanism. For example, ppp-user starts ppp, which in turn could create any number of processes, depending on the configuration, and thus any number of pid files. Then, a basic "stop" cannot be achieved, because it relies on a well-defined pid file. If you think pccardd can be improved, define pidfile in the rc script to /var/run/pccardd.pid like what is done in syslogd, it will automatically be used when stopping pccardd if you remove the stop_cmd definition. And submit a PR if you think it's worth. Cheers, --=20 Jean-Baptiste Quenot http://caraldi.com/jbq/ --zx4FCpZtqtKETZ7O Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/w2Jd9xx3BCMc9gsRAkCyAJ9UQfNHptJ9IU57sOYHs3M7LcRrkwCfSuA4 39usXyyARA8lb+wdWXe9d9A= =J6gi -----END PGP SIGNATURE----- --zx4FCpZtqtKETZ7O--