Date: Tue, 25 Nov 2003 15:08:31 +0100 From: Jean-Baptiste Quenot <jb.quenot@caraldi.com> To: freebsd-questions@freebsd.org Subject: Re: stop_cmd=":" in pccard Message-ID: <20031125140829.GD1256@watt.intra.caraldi.com> In-Reply-To: <20031124172222.GA20475@artax.karlin.mff.cuni.cz> References: <20031124172222.GA20475@artax.karlin.mff.cuni.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031125140829.GD1256>