Date: Sat, 27 Feb 2010 21:44:10 +0100 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: Freddie Cash <fjwcash@gmail.com> Cc: fs@freebsd.org Subject: Re: HAST: file name consistency Message-ID: <20100227204410.GB2586@garage.freebsd.pl> In-Reply-To: <b269bc571002251002s45ee6f0eg5455ad3249105ad7@mail.gmail.com> References: <b269bc571002251002s45ee6f0eg5455ad3249105ad7@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--f5QefDQHtn8hx44O Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 25, 2010 at 10:02:23AM -0800, Freddie Cash wrote: > Just curious: why is the config file called hast.conf, but all the RC va= rs > and scripts use hastd? Shouldn't it all be "hastd" or all "hast"? >=20 > For example, if the rc script is hastd, the rcvar is hastd_enable, should= n't > the config file be called hastd.conf, and the control program called > hastdctl? >=20 > Or, if the config file is hast.conf and the control program is hastctl, > shouldn't the rcvar and script be just hast/hast_enable? >=20 > Just seems strange to have some things called "hast" and other things cal= led > "hastd" when it's all the same program/setup. >=20 > Perhaps I'm being too pedantic? Nope, I also did some thinking about this while I was working on it. Actually the configuration file name was hastd.conf for some time, but I changed it to hast.conf at the end. The reason for hast.conf is that it is not only used by hastd(8) daemon, but also by hastctl(8) control utility, so bascially by entire HAST software. That's why hastd.conf was in my opinion confusing, as it suggested that it was only used by the hastd(8) daemon. The rc.d/hastd script is there to start hastd(8) daemon. That's the only thing it does. It doesn't even configure resources role on start using hastctl(8) (it only stops resources on shutdown). That's why script and variables are named 'hastd*' and not 'hast*'. Now hastctl name. HAST is the software (project) name. hastctl means HAST-_c_on_t_ro_l_ just like hastd means HAST-_d_aemon. hastctl doesn't only control hastd, but can do other things too, eg. initialize metadata (create subcommand) and dump metadata (dump subcommand) without communicating with hastd. Does that make sense for you? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --f5QefDQHtn8hx44O Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkuJhBoACgkQForvXbEpPzRpLwCguLgi//a2PBQLxwrzO6k8cr4H 5tgAniW3OvepALrXhww99DTWC00LEno7 =qHEe -----END PGP SIGNATURE----- --f5QefDQHtn8hx44O--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100227204410.GB2586>