Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Jul 1997 05:20:40 -0600 (MDT)
From:      Alan Lundin <aflundi@lundin.abq.nm.us>
To:        freebsd-hackers@freebsd.org
Subject:   Re: /etc/init.d/
Message-ID:  <199707111120.FAA01337@lundin.abq.nm.us.>
In-Reply-To: Christoph Kukulies <kuku@gilberto.physik.rwth-aachen.de> "Re: /etc/init.d/" (Jul 11, 11:11am)

next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 11, 11:11am, Christoph Kukulies wrote:
> Subject: Re: /etc/init.d/
> 
> On Fri, Jul 11, 1997 at 10:33:05AM +0200, Sebastian Lederer wrote:
> > J Wunsch wrote:
> > > 
> > > Well, seriously, we've got a good number of rc.something scripts
> > > already done.  It seems David Nugent is finally committing the idea of
> 
> [...]
> > 
> > Let me first say that I am very pleased with the direction the
> > FreeBSD /etc/rc model is moving. It provides the possibility
> > for additional software packages to install startup scripts without
> > fiddling with existing files, but it does not have the
> > (mostly useless) overkill complexity of the SystemV model.
> > 
> > But I would suggest that the /usr/local/etc/rc.d directory is
> > moved to /etc/rc.d.
> > 
> > Imagine a server machine running the apache httpd, which is
> > started from /usr/local/etc/rc.d, and several diskless clients,
> > nfs-mounting their filesystems (including /usr/local) from the
> 
> This is exactly what was annoying me here some time ago
> when I installed apache on a NIS/NFS server machine.
> 
> Suddenly all clients were running httpds and I had to disable
> manually on all clients to leave out /usr/local/etc/rc.d in
> $local_startup (/etc/rc.conf)
> 
> I agree with moving it to /etc/rc.d unless a better FreeBSD
> diskless/NFS concept is being developed from ground up. Actually
> there ain't any diskless strategy right now, afaik.
> 
> > server. The /etc/rc script on the clients will then see the
> > apache startup script in /usr/local/etc/rc.d. So you will
> > have a httpd process running on each client, except if you
> > modify the /etc/rc script on each client, which is 
> > not excactly what you want.
> > 
> > Moving the rc.d directory to /etc would avoid this problem,
> > since /etc is (usually) private to a single machine.

I guess I don't see what the problem with the
current system is.  Currently you can have one
script (assuming you have NFS mounting it amoung
N machines) that says:

   case `hostname` in
   $SERVER)	<startup httpd>
		;;
   esac

where if it is moved to /etc/rc.d, then you must
maintain N scripts, AND you stand more of a chance
that those scripts will get clobbered on the next
OS upgrade.

I'm afraid I'd have to say that I consider the
current system considerably more elegant than the
/etc/rc.d one being proposed.

--alan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707111120.FAA01337>