Date: Tue, 02 Oct 2007 13:16:00 +0200 From: Pietro Cerutti <gahr@gahr.ch> To: Doug Barton <dougb@FreeBSD.org> Cc: freebsd-rc@FreeBSD.org Subject: Re: conf/105568: [patch] Add more flexibility to rc.conf, to choose "_enable" values at startup Message-ID: <47022870.7030607@gahr.ch> In-Reply-To: <alpine.BSF.0.9999.0710011753400.1408@ync.qbhto.arg> References: <200710012040.l91KeC2t097859@freefall.freebsd.org> <alpine.BSF.0.9999.0710011753400.1408@ync.qbhto.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFDED252132D663577351FCB8 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Doug Barton wrote: > What do you feel is the need/benefit of adding this? I read your PR, an= d > I don't find your reasoning very compelling. You can easily start or > stop services after the system enters multi-user mode by simply changin= g > the _enable variable and running /etc/rc.d/foo start|stop as needed. > There are precious few services that depend on being started at boot ti= me. 1) enter multi user mode 2) edit rc.conf 3) /etc/rc.d/foo [start|stop] vs. 1) choose yes or no before entering multi user mode It's just a matter of comfort, cleanness and easy of handling. Here are a few examples which come to my mind right now: A student having a "web technologies" course would start its web server and database daemons only during the course. The same student, during a Linux course would start the kqemu service to load the Qemu kernel module and run a virtualized linux machine. An employee would start a VPN connection to its corporation by enabling vpnc only when working at home. On a laptop, one could start powerd only when he's running on battery or when the environment temperature is high (thus CPU clock speed should be controlled). >=20 > Also, in regards to your section about using this on a laptop, I have > solved the same problem by using an rc.local script that detects the > network I'm on and then runs anything I need with onestart. Admittedly > your solution has the benefit of properly stopping the service at > shutdown time, but I've never found that to be a problem. The discussion about the use on laptops is not only related to the networking facilities. In the few examples I posted above, I clearly assume that the machine on which these decisions are taken is a laptop. I mentioned the use on laptops on the problem report because this is clearly a matter of mobility. Moreover, being it a boot-related patch, it's not supposed to be used in a server with hundreds of days of uptime. >=20 > So can you please elaborate on your reasoning? And do others find this > to be an idea worth pursuing? Finally, I think that the potential benefits of this patch greatly exceed its negative effects (if any..). >=20 > Thanks, Thanks for your feedback! >=20 > Doug >=20 --=20 Pietro Cerutti PGP Public Key: http://gahr.ch/pgp --------------enigFDED252132D663577351FCB8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHAih3wMJqmJVx944RCtB2AKCAuKLz9o3T82asxvSmRQt2j2WlAgCfTL9j zl2W3mXxhVvmBlryqttnJzo= =Mofa -----END PGP SIGNATURE----- --------------enigFDED252132D663577351FCB8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47022870.7030607>