conf/165817: [periodic] [patch] /etc/periodic reports
misconfiguration when it shouldn' t
jhb at freebsd.org
Mon May 7 15:40:10 UTC 2012
The following reply was made to PR conf/165817; it has been noted by GNATS.
From: John Baldwin <jhb at freebsd.org>
To: bug-followup at freebsd.org,
c.kworr at gmail.com
Subject: Re: conf/165817: [periodic] [patch] /etc/periodic reports misconfiguration when it shouldn't
Date: Mon, 7 May 2012 11:15:28 -0400
This doesn't make sense. The various variables don't have a default value in
/etc/defaults/rc.conf (e.g. daily_local), so they should just be empty, and
the for loop should not do anything if the variable is empty. For example, if
you run this in /bin/sh:
$ for script in $notexists
> echo foo
You don't get any output at all. Thus, having the default configuration of
not having these variables set should never get into the loop to execute the
line you are modifying.
In your case you must have daily_local, etc. set to some absolute path that
doesn't exist (e.g. daily_local="/nonexistent") in which case that is a
misconfiguration that the scripts should warn you about.
Or is the problem that you have daily_local set to "/etc/*.local" (the glob)
and that isn't matching, so the shell runs the loop with the value
"/etc/*.local"? That is a bit harder to fix.
Your patch would not be correct if someone set "daily_local" to
"/nonexistent". That is a case that _should_ be warned about.
More information about the freebsd-bugs