Subject: Re: /etc/rc.d/virecover
To: Julio M. Merino Vidal <email@example.com>
From: Luke Mewburn <lukem@NetBSD.org>
Date: 01/10/2004 11:00:30
Content-Type: text/plain; charset=us-ascii
On Fri, Jan 09, 2004 at 11:03:25PM +0100, Julio M. Merino Vidal wrote:
| On Friday 09 January 2004 22:52, Andrew Brown wrote:
| > >Currently /etc/rc.d/virecover can't be controlled by /etc/rc.conf. I
| > >wonder if there's any reason for this.
| > >
| > >By adding "rcvar=3D$name" into /etc/rc.d/virecover, virecover=3DNO in
| > >/etc/rc.conf works as other rc.d scripts.
| > this
| > echo 'start_cmd=3D":"' > /etc/rc.conf.d/virecover
| > will work as well, and has the added advantage of not modifying the
| > rc.d scripts...
| > it's not that you can't modify them, but if you can avoid it, it's
| > better.
| Though, the question may be... why that rc.d script does not define rcv=
| while others do?
Only for historical reasons; when it was converted from /etc/rc to
/etc/rc.d/*, virecover didn't have an rc.conf(5) variable to control
The original idea is sound; add rcvar=3D$name to /etc/rc.d/virecover,
"virecover=3DYES" to /etc/defaults/rc.conf, and update the rc.conf(5)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
-----END PGP SIGNATURE-----