View source for Rcstartup, SysV vs. BSD

From Free Knowledge Base- The DUCK Project: information for everyone

← Rcstartup, SysV vs. BSD

You do not have permission to edit this page, for the following reasons:

• The action you have requested is limited to users in the group: emailconfirmed.
• This page has been protected to prevent editing or other actions.

---

You can view and copy the source of this page:

<nowiki>SysV vs. BSD: Runlevels vs. No Runlevels</nowiki> <nowiki></nowiki> <nowiki>* OpenBSD does not have runlevels. OpenBSD uses an rc(8) style startup</nowiki> <nowiki></nowiki> <nowiki>* A Unix administrator can achieve all of the functionality of runlevels </nowiki> <nowiki>without using runlevels.</nowiki> <nowiki></nowiki> <nowiki>* Whereas /etc/inittab sets the default runlevel on a Linux system, a BSD</nowiki> <nowiki>* system</nowiki> <nowiki>uses /etc/ttys to determine whether the system will boot into multiuser</nowiki> <nowiki>command </nowiki> <nowiki>line or multiuser GUI.</nowiki> <nowiki></nowiki> <nowiki>* On a Linux system, each runlevel has an associated subdirectory: rc0.d for</nowiki> <nowiki>runlevel 0, rc1.d for runlevel 1, and so on. The symlink names begin with</nowiki> <nowiki>either</nowiki> <nowiki>S (for start) or K (for kill).</nowiki> <nowiki></nowiki> <nowiki>* On OpenBSD the "system" startup scripts are found in /etc/rc.d and "user</nowiki> <nowiki>added" startup scripts in /usr/local/etc/rc.d</nowiki> <nowiki></nowiki> <nowiki>* On OpenBSD, instead of using symbolic links beginning with S or K, a handful</nowiki> <nowiki>of scripts in /etc whose names start with rc control which scripts run at</nowiki> <nowiki>startup and shutdown.</nowiki> <nowiki></nowiki> <nowiki>* Most of the scripts found in Linux's /etc/init.d and BSD's /etc/rc.d share</nowiki> <nowiki>similar behavior.</nowiki> <nowiki></nowiki> <nowiki>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *</nowiki> <nowiki>* *</nowiki> <nowiki></nowiki> <nowiki>etc/rc.conf.local is an extension of /etc/rc.conf, which is used to set</nowiki> <nowiki>variables for /etc/rc, which is run by init. Custom startup scripts belong in</nowiki> <nowiki>/etc/rc.local, which is part of the default install.</nowiki> <nowiki></nowiki> <nowiki>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *</nowiki> <nowiki>* *</nowiki> <nowiki></nowiki> <nowiki>NAME</nowiki> <nowiki> rc - command scripts for system startup</nowiki> <nowiki></nowiki> <nowiki>SYNOPSIS</nowiki> <nowiki> /etc/rc</nowiki> <nowiki> /etc/rc.local</nowiki> <nowiki> /etc/rc.securelevel</nowiki> <nowiki></nowiki> <nowiki>FILES</nowiki> <nowiki> /etc/rc Command scripts for system startup.</nowiki> <nowiki> /etc/rc.local Site specific command scripts for system startup.</nowiki> <nowiki> /etc/rc.conf System daemon configuration database.</nowiki> <nowiki> /etc/rc.conf.local Site specific daemon configuration database.</nowiki> <nowiki> /etc/rc.securelevel Commands run before the security level changes.</nowiki> <nowiki> /etc/rc.shutdown Commands run at system shutdown.</nowiki> <nowiki> /etc/login.conf Login class capability database.</nowiki> <nowiki> /etc/netstart Command script for network startup.</nowiki> <nowiki></nowiki> <nowiki>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *</nowiki> <nowiki>* *</nowiki> <nowiki></nowiki> <nowiki>In rc.conf or rc.conf.local it is sufficient to have a service startup by</nowiki> <nowiki>using the empty quotes:</nowiki> <nowiki></nowiki> <nowiki> sshd_flags="" <- this tells sshd to start with no arguments</nowiki> <nowiki> sshd_flags=NO <- sshd will not start automatically</nowiki> <nowiki></nowiki> <nowiki>You can specify startup parameters that would otherwise appear behind the</nowiki> <nowiki>binary on the command line. Example:</nowiki> <nowiki></nowiki> <nowiki> named_flags="-t /var/named -u named"</nowiki> <nowiki></nowiki> <nowiki>But sometimes an additional line is necessary, to get the service to start</nowiki> <nowiki>automatically when the system loads.</nowiki> <nowiki></nowiki> <nowiki> named_enable=YES </nowiki> <nowiki></nowiki> <nowiki>So, for bind to start on system startup it apparently requires both of the</nowiki> <nowiki>following:</nowiki> <nowiki></nowiki> <nowiki> named_flags="-t /var/named -u named"</nowiki> <nowiki> named_enable=YES</nowiki> <nowiki></nowiki> <nowiki>However, it is not cleary as to when both are required, and when only the</nowiki> <nowiki>first is required.</nowiki> <nowiki></nowiki> <nowiki>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *</nowiki> <nowiki>* *</nowiki> <nowiki></nowiki> <nowiki>10.3 - How do I start daemons with the system? (Overview of rc(8))</nowiki> <nowiki></nowiki> <nowiki>OpenBSD uses an rc(8) style startup. This uses a few key files for startup.</nowiki> <nowiki></nowiki> <nowiki> * /etc/rc - Main script. Should not be edited.</nowiki> <nowiki> * /etc/rc.conf - Configuration file used by /etc/rc to know what daemons</nowiki> <nowiki> * should start with the system.</nowiki> <nowiki> * /etc/rc.conf.local - Configuration file you can use to override settings</nowiki> <nowiki> * in /etc/rc.conf so you don't have to touch /etc/rc.conf itself, which is</nowiki> <nowiki> * convenient when upgrading your system.</nowiki> <nowiki> * /etc/netstart - Script used to initialize the network. Shouldn't be</nowiki> <nowiki> * edited.</nowiki> <nowiki> * /etc/rc.local - Script used for local administration. This is where new</nowiki> <nowiki> * daemons or host specific information should be stored.</nowiki> <nowiki> * /etc/rc.securelevel - Script which runs commands that must be run before</nowiki> <nowiki> * the security level changes. See init(8)</nowiki> <nowiki> * /etc/rc.shutdown - Script run on shutdown. Put anything you want done</nowiki> <nowiki> * before shutdown in this file. See rc.shutdown(8) </nowiki> <nowiki></nowiki> <nowiki>How does rc(8) work?</nowiki> <nowiki></nowiki> <nowiki>The main files a system administrator should concentrate on are /etc/rc.conf</nowiki> <nowiki>(or</nowiki> <nowiki>/etc/rc.conf.local), /etc/rc.local and /etc/rc.shutdown. To get a look of how</nowiki> <nowiki>the rc(8) procedure works, here is the flow:</nowiki> <nowiki></nowiki> <nowiki>After the kernel is booted, /etc/rc is started:</nowiki> <nowiki></nowiki> <nowiki> * Filesystems are checked.</nowiki> <nowiki> * Configuration variables are read in from /etc/rc.conf and, afterwards,</nowiki> <nowiki> * /etc/rc.conf.local. Settings in rc.conf.local will override those in</nowiki> <nowiki> * rc.conf.</nowiki> <nowiki> * Filesystems are mounted</nowiki> <nowiki> * Clears out /tmp and preserves any editor files</nowiki> <nowiki> * Configures the network via /etc/netstart</nowiki> <nowiki> o Configures your interfaces up.</nowiki> <nowiki> o Sets your hostname, domainname, etc. </nowiki> <nowiki> * Starts system daemons</nowiki> <nowiki> * Performs various other checks (quotas, savecore, etc)</nowiki> <nowiki> * Local daemons are run, via /etc/rc.local </nowiki> <nowiki></nowiki> <nowiki>Starting Daemons and Services that come with OpenBSD</nowiki> <nowiki></nowiki> <nowiki>Most daemons and services that come with OpenBSD by default can be started on</nowiki> <nowiki>boot by simply editing the /etc/rc.conf configuration file. To start out take</nowiki> <nowiki>a</nowiki> <nowiki>look at the default /etc/rc.conf file. You'll see lines similar to this:</nowiki> <nowiki></nowiki> <nowiki> ftpd_flags=NO # for non-inetd use: ftpd_flags="-D"</nowiki> <nowiki></nowiki> <nowiki>A line like this shows that ftpd is not to start up with the system (at least</nowiki> <nowiki>not via rc(8), read the Anonymous FTP FAQ to read more about this). In any</nowiki> <nowiki>case,</nowiki> <nowiki>each line has a comment showing you the flags for NORMAL usage of that daemon</nowiki> <nowiki>or</nowiki> <nowiki>service. This doesn't mean that you must run that daemon or service with those</nowiki> <nowiki>flags. Read the relevant manual page to see how you can have that daemon or</nowiki> <nowiki>service start up in any way you like. For example, here is the default line</nowiki> <nowiki>pertaining to httpd(8).</nowiki> <nowiki></nowiki> <nowiki> httpd_flags=NO # for normal use: "" (or "-DSSL" after reading</nowiki> <nowiki>ssl(8))</nowiki> <nowiki></nowiki> <nowiki>Here you can obviously see that starting up httpd normally no flags are</nowiki> <nowiki>necessary. So a line like: " httpd_flags=""" would be necessary. But to start</nowiki> <nowiki>httpd with ssl enabled. (Refer to the SSL FAQ or ssl(8)) You should start with</nowiki> <nowiki>a</nowiki> <nowiki>line like: "httpd_flags="-DSSL"".</nowiki> <nowiki></nowiki> <nowiki>A good approach is to never touch /etc/rc.conf itself. Instead, create the</nowiki> <nowiki>file</nowiki> <nowiki>/etc/rc.conf.local, copy just the lines you are about to change from</nowiki> <nowiki>/etc/rc.conf and adjust them as you like. This makes future upgrades easier --</nowiki> <nowiki>all the changes are in the one file.</nowiki> <nowiki>Starting up local daemons and configuration</nowiki> <nowiki></nowiki> <nowiki>For other daemons which you might install on the system via packages or other</nowiki> <nowiki>ways, you should use the /etc/rc.local file. For example, I've installed a</nowiki> <nowiki>daemon which lies at /usr/local/sbin/daemonx. I want it to start at boot time.</nowiki> <nowiki>I</nowiki> <nowiki>would put an entry into /etc/rc.local like this:</nowiki> <nowiki></nowiki> <nowiki> if [ -x /usr/local/sbin/daemonx ]; then</nowiki> <nowiki> echo -n ' daemonx'; /usr/local/sbin/daemonx</nowiki> <nowiki> fi</nowiki> <nowiki></nowiki> <nowiki>(If the daemon does not automatically detach on startup, remember to add a "&"</nowiki> <nowiki>at the end of the command line.)</nowiki> <nowiki></nowiki> <nowiki>From now on, this daemon will be started at boot. You will be able to see any</nowiki> <nowiki>errors on boot, a normal boot with no errors would show a line like this:</nowiki> <nowiki></nowiki> <nowiki> Starting local daemons: daemonx.</nowiki> <nowiki></nowiki> <nowiki>rc.shutdown</nowiki> <nowiki></nowiki> <nowiki>/etc/rc.shutdown is a script that is run at shutdown. Anything you want done</nowiki> <nowiki>before the system shuts down should be added to this file. If you have apm,</nowiki> <nowiki>you</nowiki> <nowiki>can also set "powerdown=YES", which will give you the equivalent of "shutdown</nowiki> <nowiki>-p".</nowiki> <nowiki></nowiki> <nowiki></nowiki> [[Category:Computer_Technology]] [[Category:OpenBSD]]

Return to Rcstartup, SysV vs. BSD.