[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: rc.local
- From: Chuck Yerkes <chuck+obsd_(_at_)_2003_(_dot_)_snew_(_dot_)_com>
- Date: Thu, 16 Jan 2003 21:20:03 -0500
- Mail-followup-to: Chuck Yerkes <chuck+obsd_(_at_)_2003_(_dot_)_snew_(_dot_)_com>, misc_(_at_)_openbsd_(_dot_)_org
- Reply-to: misc_(_at_)_openbsd_(_dot_)_org
Quoting Chris Gripp (cgripp_(_at_)_automotive_(_dot_)_com):
> Does /etc/init.d/ even exist in OpenBSD?!?
> None of my installs have it. I'm not asking to be a smartass. I am used to
> the Linux SysV system and although I am getting used to BSD quickly it is a
> little different. If there were simple scripts for starting, stoping and
> restarting daemons like there were in linux for bsd that would be keen.
No, as I said, "in my personal practice".
I advocated it here once. Once. Long ago. Having
startup/shutdown scripts was perceived to be the first
step on the slippery slope to changing the kernel and
license to be a System 5 Unix. Several reactions went
irrational. To be expected. "So how you you plan to implement
init levels?" (well, I don't, I just have /etc/rc run
init scripts getting flags and yeah/nay from from /etc/rc.conf.
It made it quite managable by automatic tools).
Writing start/stop scripts is pretty simple. Really simple.
If you've seen several unixes, you can do it.
OpenBSD would appear to be the BSD that's not moving to
init scripts, NetBSD and FreeBSD 5 mostly use them - it makes
it easier for 3rd parties (and ports) to add their services
to the startup. Good behavior says to add in an "OFF" position
(e.g. install imap.sh.sample).
It's not generally a problem either way. I make my own scripts in
the init.d/ form and have rc.local call them. Just personal
The stanzas for rc and rc.local are pretty straight forward.
Best practices suggest clear naming of the service (e.g. MYSQL)
and a flags variable that's used for all parameters.
One day, someone might write something to manage rc.conf.
SGI's chkconfig does ok with system 5 (multiple init levels),
but I have no clue why Linus went with that model rather than
the BSD single/multiple user model which is all most people use.
> -----Original Message-----
> From: Chuck Yerkes [mailto:chuck+obsd_(_at_)_2003_(_dot_)_snew_(_dot_)_com]
> Sent: Thursday, January 16, 2003 1:32 PM
> To: misc_(_at_)_openbsd_(_dot_)_org
> Subject: Re: rc.local
> It's a shell script.
> Feel free to take a look at how rc starts things.
> Put that into your own shell script.
> Run it. Did it work? fix it, repeat until it works.
> Then put it into your rc.local.
> I actually like an "rc.local.`hostname -s`" that never
> gets overwritten in upgrades. It's called at the end of
> rc.local. In a very large environment, I created
> "rc.local.`domainname`" as well so we could have per
> domains startups pushed out and per-machine things.
> In my personal practice, I just keep startup/shutdown
> scripts in /etc/init.d/ and have a loop in rc.local
> start them all up. It means that Joe Jr System admin
> can be told to "restart postgres" without having to
> understand all the details and without me working about
> a mistake. That's just a personal preference.
> Quoting scott (scott_(_at_)_sporticia_(_dot_)_com):
> > hi
> > does anyone have some good web links where I can read about the syntax
> > for rc.local for OpenBSD ??
> > I tried to add safe_mysqld into the startup, copying the syntax of what
> > was already in there, but it causes my box to fall over on reboot :o(
> > I've tried a google search, but it doesn't turn up very much that is
> > solid OpenBSD syntax, I get quite a lot of Linux and /etc/init.d stuff
> > instead
> > thanks
> > _scott