Date: Fri, 6 Jan 2006 16:42:40 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Doug Barton <dougb@FreeBSD.org> Cc: Brooks Davis <brooks@one-eyed-alien.net>, Mike Jakubik <mikej@rogers.com>, ports@FreeBSD.org, martines@rochester.rr.com Subject: Re: FreeBSD Port: sysutils/smartmontools (more RCng problems) Message-ID: <20060107004240.GA30545@odin.ac.hmc.edu> In-Reply-To: <43BF0976.703@FreeBSD.org> References: <43BDB619.5020104@rogers.com> <43BF02F1.6050007@FreeBSD.org> <20060107001405.GA27713@odin.ac.hmc.edu> <43BF0976.703@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--G4iJoqBmSsgzjUCe
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Jan 06, 2006 at 04:21:10PM -0800, Doug Barton wrote:
> Brooks Davis wrote:
> >On Fri, Jan 06, 2006 at 03:53:21PM -0800, Doug Barton wrote:
> >>Mike Jakubik wrote:
> >>>This is yet another port that does not work properly because of the=20
> >>>recent RCng commits in 6-STABLE. Smartd does not startup on bootup, it=
=20
> >>>has to be manually started.
> >>Ok, I installed this port and tested it myself, and the problem is the=
=20
> >>hard coded value of smartd_enable at the top of the script. For reasons=
I=20
> >>don't quite understand yet, hard coding the value in the script affects=
=20
> >>the boot-time operation of the script differently than on the command=
=20
> >>line.
> >
> >The reason the two cases behave differently is that during boot
> >the initial call to load_rc_config in /etc/rc causes /etc/rc.conf
> >to be read and there after the fact that it's read it cached.
>=20
> *slaps forehead* Right-o, forgot about the caching. Thanks for the=20
> reminder.
>=20
> >/etc/rc.conf.d/"$name" will be read, but I doubt there are many users
> >of that feature. The variables need to be set if and only if they are
> >unset after load_rc_config is run like so:
>=20
> That's the case with ports, which don't have default values.
Yes. In some ways I think the ideal thing would be a search for per
command default files...
> > load_rc_config ${name}
> >
> > foo_enable=3D${foo_enable-NO}
> >
> > run_rc_command "$1"
> >
> >Someone (mtm IIRC) told me to use the -NO as opposed to the :-NO syntax
> >because empty, but defined values should not be overridden. I believe
> >that is the correct thing to do.
>=20
> That makes sense. That syntax isn't documented in the sh man page, but it=
=20
> probably should be.
Yes. I ended up writing a short script just to check the syntax before
sending that message because there were no docs.
-- Brooks
--=20
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
--G4iJoqBmSsgzjUCe
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFDvw6AXY6L6fI4GtQRAkf/AKCR5y32Kz2Fp/UUUbzTeua7F9ap6wCeLLbi
EuFbLs7AiDY/Wzw/VQvEr5w=
=Y0TH
-----END PGP SIGNATURE-----
--G4iJoqBmSsgzjUCe--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060107004240.GA30545>