On Fri, Jan 20, 2012 at 03:06:02PM +0400, Eygene Ryabinkin wrote: > Thu, Jan 19, 2012 at 11:27:59AM -0600, Brooks Davis wrote: > > Arguably it should be moved to /libexec since it's not an rc.d > > script and simply uses the framework because it had similar needs > > Well, I fear that some user scripts may rely on the dhclient path > to be /etc/rc.d/dhclient, so such a change could lead to the POLA > violation. So, all pros and cons of such a change should be carefully > weighted. What is the gain from moving it to /libexec apart from > avoiding pollution of /etc/rc.d by non-rc.d scripts? It is a good > thing to have for the clear design, but having dhclient in /etc/rc.d > has no effect on the boot process, since it is marked 'nostart' and > it allows people to use 'service dhclient restart $if' without hacking > the service to still allow to use this command. We can, of course, > move it to /libexec/rc.d/ and add this path to the local_startup, but > I doubt that this approach will give any real gain, though I can be > missing some important points.
That's basically why I didn't move it in the first place. It's clearly in the wrong place, but people will expect it there so there isn't much point in moving it. -- Brooks
pgpD2NkIJbCLx.pgp
Description: PGP signature
