Date: Tue, 3 Jun 2008 13:19:37 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-ports@freebsd.org Cc: Paul Schmehl <pschmehl_lists_nada@tx.rr.com> Subject: Re: Problems with startup scripts Message-ID: <20080603131937.192622ee@gumby.homeunix.com.> In-Reply-To: <765B879956FB90DA571FA609@Macintosh.local> References: <765B879956FB90DA571FA609@Macintosh.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 02 Jun 2008 22:13:15 -0500
Paul Schmehl <pschmehl_lists@tx.rr.com> wrote:
> Imagine my surprise when I discovered that *all* of my startup
> scripts=20 were running double flags!
>
> So, I looked at /etc/rc.subr, and lo and behold:
> Line 670 of /etc/rc.subr has "$command $rc_flags $command_args"
>
> So, the question is, is this an error in rc_subr? Or was I
> misinformed=20 about the use of cammand_args? If the former, do I
> submit a PR? If the=20 latter, I have a lot of work to do.
> {{{sigh}}}
rc.subr seems to be self-consistent, if you look in the comments where
these variables are documented.
There are a number of /etc/rc.d scripts that follow similar usage, but
they are mostly using flag variable names that don't match
"${name}_flags". The exception is auditd which presumably would
get double flags, if it were actually given any.
$ grep -Ei "command_args.*=.*flags" /etc/rc.d/*
/etc/rc.d/auditd:command_args="${auditd_flags}"
/etc/rc.d/nfsd:command_args="${nfs_server_flags}"
/etc/rc.d/ypbind:command_args="${nis_client_flags}"
/etc/rc.d/yppasswdd:command_args="${nis_yppasswdd_flags}"
/etc/rc.d/ypserv:command_args="${nis_server_flags}"
/etc/rc.d/ypset:command_args="${nis_ypset_flags}"
/etc/rc.d/ypxfrd:command_args="${nis_ypxfrd_flags}"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080603131937.192622ee>