Template:Article summary start
Template:Article summary text
Template:Article summary heading
Template:Article summary wiki
Template:Article summary end
/etc/rc.conf is the configuration file for Arch's initscripts. It configures what daemons to start at boot, the basic network daemon, and certain aspects of hardware discovery.
This is what a typical
rc.conf file looks like on an up-to-date Arch install. (current version):
# # /etc/rc.conf - configuration file for initscripts # # Most of rc.conf has been replaced by various other configuration # files. See archlinux(7) for details. # # For more details on rc.conf see rc.conf(5). # DAEMONS=(syslog-ng network crond) # Storage # # USEDMRAID="no" # USELVM="no" # Network # # interface= # address= # netmask= # gateway=
New configuration file
In the past, this file also used to contain configurations for other parts of the system. Unless you are using an alternate init system like systemd,
/etc/rc.conf configures which daemons to start during boot-up and some networking and storage information.
|Configuration||Configuration file(s)||Legacy rc.conf section|
|Console fonts and keymap||
Configuration files can simply be created if they do not exist already and you wish to change the defaults.
- A space-separated list of scripts located in
/etc/rc.d/which are started during the boot process. Usually you do not need to change the defaults to get a running system, but you are going to edit this array whenever you install system services like
sshd, and want to start these automatically during boot-up. This is basically Arch's way of handling what others handle with various symlinks to an
init.ddirectory. For more info see: Writing rc.d scripts
- If a script name is prefixed with a bang (
!), it is not executed.
- If a script is prefixed with an "at" symbol (
@), then it will be executed in the background, i.e. the startup sequence will not wait for successful completion before continuing.
- If a script name is prefixed with a bang (
DAEMONS=(@syslog-ng !network net-profiles crond sshd)
- Scan for FakeRAID (dmraid) Volumes at startup (runs
dmraid -i -ay).
- Scan for LVM volume groups at start-up, which is required if you use LVM. Setting to
vgchange --sysinit -a y(handled by activate_vgs() function) during sysinit.
rc.conf only supports the configuration of a single interface. For the configuration of multiple interfaces or other advanced network configurations like bridging, use netcfg.
- name of device (required)
- IP address (leave blank for DHCP)
- subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
- broadcast address (ignored for DHCP) (optional)
- default route (ignored for DHCP)
Static IP Example
interface=eth0 address=192.168.0.2 netmask=255.255.255.0 broadcast=192.168.0.255 gateway=192.168.0.1
interface=eth0 address= netmask= gateway=
UTCtime, or the
localtime. If this value is not set, then the value stored by hwclock in
/var/lib/hwclock/adjtimeis used instead. See Time for more information.
Specifies whether the hardware clock, which is synchronized from on bootup and to on shutdown, stores
UTCmakes sense because it greatly simplifies changing timezones and daylight savings time. Linux will change to-and-from DST, regardless of whether Linux was running at the time DST is entered or left.
localtimeis necessary if you dual boot with an operating system that only stores
localtime, such as Windows. Linux will not adjust the time, operating under the assumption that your system may be a dual-boot system at that time and that the other OS takes care of the DST switch. If that was not the case, the DST change needs to be made manually.
- empty: fall back to the value in
/var/lib/hwclock/adjtime, which defaults to UTC. This is recommended as other users of hwclock might change the adjtime file and hence cause rc.conf and adjtime to be out of sync
- any other value will result in the hardware clock being left untouched (useful for virtualization)
/usr/share/zoneinfo. For example, a German timezone would be
Europe/Berlin, which refers to the file
Specifies your time zone. Possible time zones are the relative path to a zoneinfo file starting from the directory
/usr/share/kbd/keymaps. The keyboard layout you want to use. If you live in the US, you probably use qwerty, which is referred using us (default). The available keymaps are in
setfontprogram on boot-up (ter-v14b for example). Possible fonts are found in
/usr/share/kbd/consolefonts(only needed for non-US).
/etc/vconsole.conftakes precedence. For more info see: Console fonts
Defines the console font to load with the
setfontprogram on boot-up (8859-1_to_uni for example). Possible maps are found in
/usr/share/kbd/consoletrans. You will want to set this to a map suitable for your locale (8859-1 for Latin1, for example) if you use an utf8 locale above and use programs that generate 8-bit output.
Defines the console map to load with the
locale -afrom the command line. This setting's default is fine for US English users. The
/etc/locale.conftakes precedence if it is set, and users of login shells that cannot source
/etc/rc.conf, should set that value instead.
This sets your system language, which will be used by all i18n-friendly applications and utilities. You can get a list of the available locales by running
$LOCALEas the locale during daemon startup and during the boot process. If set to no, the C locale is used. Default value is yes.
If set to yes, use
- Enable (or disable) colorized status messages during boot-up.
/etc/hosts. The contents of
/etc/hostname(if not empty) takes precedence. Set this to the hostname of the machine, without the domain part. This is totally your choice, as long as you stick to letters, digits and a few common special characters like the dash. Should also be put in
/etc/hostname, no need to use "HOSTNAME" variable. Read more.
NETWORK_PERSIST variable tells the system whether or not to skip network shutdown. This is required if your root device is on NFS. The default setting is "no".
# default NETWORK_PERSIST="no" # NFS-based root device # NETWORK_PERSIST="yes"