Date: Tue, 22 Aug 2006 09:39:38 -0500 From: Brooks Davis <brooks@one-eyed-alien.net> To: David Thompson <dat1965@yahoo.com> Cc: freebsd-rc@freebsd.org Subject: Re: /etc/rc.d/ypxfrd REQUIRE needs updating Message-ID: <20060822143938.GB12125@lor.one-eyed-alien.net> In-Reply-To: <20060822003720.20753.qmail@web55101.mail.re4.yahoo.com> References: <20060822003720.20753.qmail@web55101.mail.re4.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Mon, Aug 21, 2006 at 05:37:20PM -0700, David Thompson wrote:
> Hi,
>
> I see that /etc/rc.d/ypxfrd has,
>
> # PROVIDE: ypxfrd
> # REQUIRE: rpcbind
>
> but ypxfrd_precmd() does a forcestart on both rpcbind and
> ypserv,
>
> ypxfrd_precmd()
> {
> if ! checkyesno rpcbind_enable && \
> ! /etc/rc.d/rpcbind forcestatus 1>/dev/null 2>&1
> then
> force_depend rpcbind || return 1
> fi
> if ! checkyesno nis_server_enable && \
> ! /etc/rc.d/ypserv forcestatus 1>/dev/null 2>&1
> then
> force_depend ypserv || return 1
> fi
>
> _domain=`domainname`
> if [ -z "$_domain" ]; then
> warn "NIS domainname(1) is not set."
> return 1
> fi
> }
>
> So why isn't ypserv part of ypxfrd's REQUIRE?
>
> Using 'REQUIRE: rpcbind ypserv' would make /etc/rc
> naturally execute ypserv before ypxfrd, courtesy of
> rcorder.
This sounds correct. This example highlights one the weakness of rc.d
vs Apple's startup scripts. We only have a way to control ordering, not a
way say "don't start _this_ if _that_ didn't start".
-- Brooks
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
iD8DBQFE6xcpXY6L6fI4GtQRAsP6AJ9C02QM8kv1hcTFUcJv9TNvrRgPZQCeMgm2
GMaaO1wsQRHidNs8PzYSIAw=
=389/
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060822143938.GB12125>